[Mono-bugs] [Bug 81364][Nor] New - DateTime XML serialization 'incompatible' with MS

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Thu Apr 12 16:51:04 EDT 2007

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 h at ymos.net.


--- shadow/81364	2007-04-12 16:51:04.000000000 -0400
+++ shadow/81364.tmp.5912	2007-04-12 16:51:04.000000000 -0400
@@ -0,0 +1,49 @@
+Bug#: 81364
+Product: Mono: Class Libraries
+Version: 1.2
+OS: All
+OS Details: 
+Status: NEW   
+Priority: Normal
+Component: System
+AssignedTo: mono-bugs at ximian.com                            
+ReportedBy: h at ymos.net               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+Summary: DateTime XML serialization 'incompatible' with MS
+Please fill in this template when reporting a bug, unless you know what you
+are doing.
+Description of Problem:
+If a DateTime variable is serialized on mono using a XMLSerializer, the
+result gets one more trailing character at the end of the string compared
+to the same DateTime serialized on windows (.Net). This leads to different
+string length if serializing on linux than on windows (MS). A problem
+arises if the output is used for signing of XML produced on mono (linux)
+and tested / used on windows. 
+Steps to reproduce the problem:
+1. create class with at least one DateTime variable
+2. assign it the value: 2007-04-12 14:30:39.117503+02:00 (or so)
+2. serialize the class to XML on mono under Linux
+3. serialize the class to XML on MS under windows 
+4. compare the string length of the outputs
+Actual Results:
+Expected Results:
+-> notice the missing '0' before the plus sign! 
+How often does this happen? 
+Additional Information:
+Well, 'incompatible' is not really true, since XML serialized can be read
+and deserialized on MS, but sometimes it is important for both sides to be
+exactly the same - as for signing f.e.

More information about the mono-bugs mailing list