[Mono-bugs] [Bug 82400][Nor] Changed - DateTime binary serialization incompatible with MS.NET 2.0

[bugzilla-daemon at bugzilla.ximian.com]

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 jaebird at gmail.com.

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

--- shadow/82400	2007-08-17 19:28:41.000000000 -0400
+++ shadow/82400.tmp.6017	2007-08-17 19:35:00.000000000 -0400
@@ -10,13 +10,13 @@
 Component: CORLIB
 AssignedTo: mono-bugs at ximian.com                            
 ReportedBy: jaebird at gmail.com               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
 URL: 
-Cc: alan.mcgovern at gmail.com,knocte at gmail.com,robertj at gmx.net
+Cc: alan.mcgovern at gmail.com,knocte at gmail.com,miguel at ximian.com,robertj at gmx.net
 Summary: DateTime binary serialization incompatible with MS.NET 2.0
 
 Please fill in this template when reporting a bug, unless you know what you
 are doing.
 Description of Problem:
 
@@ -131,6 +131,21 @@
 serialize and deserialize DateTime primitive type.
 
 ------- Additional Comments From jaebird at gmail.com  2007-08-17 19:28 -------
 Created an attachment (id=19830)
 Capture log of data received from .NET 2.0 Remoting client.
 
+
+------- Additional Comments From jaebird at gmail.com  2007-08-17 19:35 -------
+From the log (attached above) it appears that binary serialization
+through ISerializable is not happening. This means that my hack is
+actually a fix!
+
+This means that once the ObectWriter is changed to match. This will be
+a patch. It also means that the ISerializable interface is NOT
+required for remoting, since remoting does not use it.
+
+Summary:
+
+Maybe add a special constructor that the ObejctReader.cs uses to build
+the object from remoting. Then change ObjectWriter.cs so that it can
+round trip with the extra DateTimeKind as well.