I advise people to give up bending their business object models to work with XmlSerializer. The constraints are pretty heavy...
http://www.windojitsu.com/blog/zenandtheartofxmlserializer.html In addition to the need for public default ctors and public visibility on all serializable fields, there are more subtle limitations you may run into, down the road -- like, losing instance-identity (eg, two different fields pointing to the same object) or not being able to serialize/deserialize an object graph. Cheers, -Shawn http://msdn.com/tabletpc http://windojitsu.com =================================== 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
