Please do not reply to this email- if you want to comment on the bug, go to the URL shown below and enter your comments there.
Changed by [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=75346 --- shadow/75346 2005-06-22 01:01:26.000000000 -0400 +++ shadow/75346.tmp.11170 2005-06-22 01:01:26.000000000 -0400 @@ -0,0 +1,57 @@ +Bug#: 75346 +Product: Mono: Class Libraries +Version: 1.1 +OS: +OS Details: +Status: NEW +Resolution: +Severity: +Priority: Normal +Component: CORLIB +AssignedTo: [EMAIL PROTECTED] +ReportedBy: [EMAIL PROTECTED] +QAContact: [EMAIL PROTECTED] +TargetMilestone: --- +URL: +Cc: +Summary: MS .NET serialization compatability + +Description of Problem: +when serializing some objects from the System.Collections namespace in +ms.net platform, and then trying to deserialize on mono platform, the +process fails. +the classes that fails are: + +System.Collections.CaseInsensitiveComparer +System.Collections.CaseInsensitiveHashCodeProvider +System.Collections.DictionaryEntry +System.Collections.SortedList +System.Collections.Stack +System.Collections.BitArray + + +Steps to reproduce the problem: + +execute the next step on ms.net platform +1. for each class above create an instance and serialize it + +execute the next step on mono platform +1.for each xml, try to deserialize the object + + +Actual Results: +the deserializatino fails for these objects + +Expected Results: +The serializatino should work fine, since mono should be compatible with +ms.net platform + +How often does this happen? +every time + +Additional Information: + +Soap serialization uses reflection to serialize the objects. +mono implementation uses different data members than ms.net +implementation in some classes, and it causes the serialization to be +different. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
