"My personal preference is to only create DTO classes when they are needed, hopefully saving time on creating both the DTO objects and the code to map my domain properties to them."
Are you really saving *that* much time by taking on all the bad things that happen because of this? If it is a substantial portion of your time that would mean that you are heads down coding CRUD stuff by hand where typing speed becomes valuable? Could you code generate this kind of stuff? Is there an easier way of handling this type of code than using a domain model? Cheers, Greg On Thu, Feb 5, 2009 at 6:33 AM, Richard (Google) <[email protected]> wrote: > > Some thoughts on passing domain objects over WCF ... > > http://broloco.blogspot.com/2009/02/sending-domain-objects-across-wire.html > > Just my tuppence worth. > > Regards, > Richard > > > > > > -- It is the mark of an educated mind to be able to entertain a thought without accepting it. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" 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/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
