> losing instance-identity (eg, two different fields > pointing to the same object) or not being able to > serialize/deserialize an object graph.
I'll second this. I'm just completing a project where I needed to XML-serialise an object graph containing cross-references, back-pointers and specialised collection behaviour. To perform serialisation directly on the "proper" object model would (a) have been horrific and complicated and (b) would have required ugly compromises to the API. It's a bonus when you can use your business object model directly as a serialisation format, but it doesn't always pan out. Splitting out the serialisation format from the behavioural API made life so much easier and the business object API so much nic-- er, less horrible. -- Ivan Towlson White Carbon -----Original Message----- From: Unmoderated discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] Behalf Of Shawn A. Van Ness Sent: 18 November 2004 17:45 To: [EMAIL PROTECTED] Subject: Re: [ADVANCED-DOTNET] XML public property and constructor serialization issues. I advise people to give up bending their business object models to work with XmlSerializer. =================================== This list is hosted by DevelopMentorŪ http://www.develop.com Some .NET courses you may be interested in: Essential .NET: building applications and components with C# November 29 - December 3, in Los Angeles http://www.develop.com/courses/edotnet View archives and manage your subscription(s) at http://discuss.develop.com
