Thanks, Glenn, that was my next question, especially since this same project has MVC as well, and I'm already bored bored bored with writing DTOs.
--Stevi On Thu, Jun 24, 2010 at 10:32 AM, Glenn Block <[email protected]> wrote: > You might want to look at AutoMapper if you are concerned about > polluting your domain model. > > On 6/24/10, Stevi Deter <[email protected]> wrote: >> So, I'm faced with having to have WCF DataContracts for my domain >> model objects. I'm wondering if the best practice is to suck it up and >> have a separate class with the DataContract and write the necessary >> transfer logic, or go fast and light and annotate my domain objects. I >> suspect I know the answer, just looking for some feedback from anybody >> else who has pondered the question. >> >> --Stevi >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Seattle area Alt.Net" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/altnetseattle?hl=en. >> >> > > -- > Sent from my mobile device > > -- > You received this message because you are subscribed to the Google Groups > "Seattle area Alt.Net" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/altnetseattle?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Seattle area Alt.Net" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/altnetseattle?hl=en.
