Unfortunately the serialize.cs tool derives the serialization schema by creating an object then serializing it. If someone can tell me how to reliably derive the schema via static Reflection (ie without the need to create an object), then I'll add the comparison to corcompare (and the class-status pages).
Piers. -----Original Message----- From: Miguel de Icaza [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 24, 2002 3:58 AM To: Lawrence Pit Cc: [EMAIL PROTECTED] Subject: Re: [Mono-list] serialization > Could someone explain why this is "pretty straight forward" code?? > I'm probably missing something as I think this is one of the hardest > things to accomplish yet with mono (assuming that objects serialized > with mono must be able to deserialize using the MS .Net runtime and > vice versa). Duncan wrote a tool (mcs/tools/serialize.cs) that helps you with this. Basically it tells you what fields must be serialized and the key names that you have to use. Duncan said last night `I will write a serialization howto', as he did most of the existing serialization support in Mono. Something that I believe we have not done is make sure that classes that are tagged as `Serializable' have the same field names as their .NET counterparts. Since these will be automatically serialized, and Reflection will be used to serialize them, we need to make our fields have the same names as the .NET ones do. Miguel _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
