The XML serialiser ignores ISerializable. There is an interface IXmlSerializable which does affect XML serialisation, but I believe this has some oddities in an ASP.NET scenario. Basically, because the serialisation is done in user code, ASP.NET can't know the schema of the generated XML, so can't provide WSDL for clients to generate suitable proxies. If I remember rightly it falls back to presenting all IXmlSerializable classes as DataSets.
Also, it's unsupported at 1.1, though it becomes official in 2.0 so this isn't a particularly serious concern. -- Ivan Towlson White Carbon -----Original Message----- From: Unmoderated discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] Behalf Of Eric Means Sent: 18 November 2004 15:11 To: [EMAIL PROTECTED] Subject: Re: [ADVANCED-DOTNET] XML public property and constructor serialization issues. I believe that you can implement ISerializable and add a protected constructor with a specific signature to get around your problems. For instance, here's an EventArgs class: =================================== 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
