tag:blogger.com,1999:blog-652174954000901332.post6005016112150530727..comments2010-07-13T09:36:58.927+01:00Øyvind Vallandhttp://www.blogger.com/profile/17595718624373482981noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-652174954000901332.post-69500208548288994922010-07-13T09:36:58.918+01:002010-07-13T09:36:58.918+01:00Hi Thomas,<br /><br />I wrote this a while back - and have found a better way since then. Have a look at AutoMapper - http://automapper.codeplex.com/ - it will do the trick for you I think.Øyvind Vallandhttp://www.blogger.com/profile/17595718624373482981noreply@blogger.comtag:blogger.com,1999:blog-652174954000901332.post-73675238304136530202010-07-13T09:11:16.435+01:002010-07-13T09:11:16.435+01:00&quot; These two classes shared a number of properties and because of this their common interface was abstracted out. And this led to really easy translation, because the translator could simply translate treat two types implementing the same interface as the same type.&quot;<br /><br />That is a great idea :) unfortunately this is not a option in my case, since I don&#39;t have full control over the buisness entities. How do you usually implement translation when buisness entities and datacontracts are very different? Have you tried Microsoft&#39;s entity translator? (http://msdn.microsoft.com/en-us/library/ff647889.aspx) Or do you think manualle mapping the objects is the best way?Thomasnoreply@blogger.com