[Mono-bugs] [Bug 58787][Blo] New - Hashtable serialized by Mono is incompatible with deserializer of Microsoft CLR [maybe other classes too]

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Fri, 21 May 2004 03:14:02 -0400 (EDT)


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 paf@design.ru.

http://bugzilla.ximian.com/show_bug.cgi?id=58787

--- shadow/58787	2004-05-21 03:14:02.000000000 -0400
+++ shadow/58787.tmp.28964	2004-05-21 03:14:02.000000000 -0400
@@ -0,0 +1,75 @@
+Bug#: 58787
+Product: Mono: Class Libraries
+Version: unspecified
+OS: All
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: Unknown
+Priority: Blocker
+Component: System
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: PAF@design.ru               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: Hashtable serialized by Mono is incompatible with deserializer of Microsoft CLR [maybe other classes too]
+
+Description of Problem:
+server part runs on Mono, client part on Microsoft.Net implementation.
+they need to exchange info.
+am trying to use Serialize|Deserialize to do that
+
+Steps to reproduce the problem:
+1. serializing some data on Mono
+2. transferring it to box with Microsoft.Net
+3. deserializing data there
+
+Actual Results:
+System.Runtime.Serialization.SerializationException: Type is not resolved 
+for member System.Collections.Hashtable+SynchedHashtable, mscorlib, 
+Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089.
+at System.Runtime.Serialization.Formatters.Binary.ObjectReader.GetType
+(BinaryAssemblyInfo assemblyInfo, String name)
+at System.Runtime.Serialization.Formatters.Binary.ObjectMap..ctor(String 
+objectName, String[] memberNames, BinaryTypeEnum[] binaryTypeEnumA, Object
+[] typeInformationA, Int32[] memberAssemIds, ObjectReader objectReader, 
+Int32 objectId, BinaryAssemblyInfo assemblyInfo, SizedArray 
+assemIdToAssemblyTable)
+at System.Runtime.Serialization.Formatters.Binary.ObjectMap.Create(String 
+name, String[] memberNames, BinaryTypeEnum[] binaryTypeEnumA, Object[] 
+typeInformationA, Int32[] memberAssemIds, ObjectReader objectReader, Int32 
+objectId, BinaryAssemblyInfo assemblyInfo, SizedArray 
+assemIdToAssemblyTable)
+at 
+System.Runtime.Serialization.Formatters.Binary.__BinaryParser.ReadObjectWit
+hMapTyped(BinaryObjectWithMapTyped record)
+at 
+System.Runtime.Serialization.Formatters.Binary.__BinaryParser.ReadObjectWit
+hMapTyped(BinaryHeaderEnum binaryHeaderEnum)
+at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.Run()
+at System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize
+(HeaderHandler handler, __BinaryParser serParser, Boolean fCheck, 
+IMethodCallMessage methodCallMessage)
+at 
+System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize
+(Stream serializationStream, HeaderHandler handler, Boolean fCheck, 
+IMethodCallMessage methodCallMessage)
+at 
+System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize
+(Stream serializationStream)
+at ArtLebedev.Imprimatur2.Loader.SocketReaderWriter.ReadObject()
+
+Expected Results:
+normal deserialization.
+and overall compatibility of mono<=>ms libraries in serialization format.
+
+Additional Information:
+I noted in SSCLI sources that there class is named "SynchHashtable", 
+not "SynchedHashtable" (as it is in Mono).
+is it just ONE name of internal class that mismatches,
+Or the problem is wider [several name mismatches, major serialize formats 
+difference]?
+
+2. can I hope this will be done in some near future?