You know the answer... Ask yourself. What will happen in six months when I want to change my domain object?
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Stevi Deter Sent: Thursday, June 24, 2010 9:43 AM To: [email protected] Subject: WCF Data Contracts 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. -- 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.
