[Mono-bugs] [Bug 76808][Nor] Changed - Not expected behavior deserializing complex object with XmlSerializer

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Mon Dec 5 18:23:57 EST 2005

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 robertj at gmx.net.


--- shadow/76808	2005-12-05 16:40:34.000000000 -0500
+++ shadow/76808.tmp.31371	2005-12-05 18:23:57.000000000 -0500
@@ -1,13 +1,13 @@
 Bug#: 76808
 Product: Mono: Class Libraries
 Version: 1.1
 OS: unknown
 OS Details: Microsoft Windows XP SP2
-Status: RESOLVED   
-Resolution: FIXED
+Status: REOPENED   
 Severity: Unknown
 Priority: Normal
 Component: Sys.XML
 AssignedTo: lluis at ximian.com                            
 ReportedBy: leiszen.daniel at chello.hu               
 QAContact: mono-bugs at ximian.com
@@ -76,6 +76,29 @@
 has been filled.
 ------- Additional Comments From lluis at ximian.com  2005-12-05 16:40 -------
 Fixed in SVN (r53949). Now collections will be reused if they already
 exist, like in MS.NET.
+------- Additional Comments From robertj at gmx.net  2005-12-05 18:23 -------
+The problem is still there in one case.
+The attached test case prints under mono:
+set new list? True
+item count: 3
+Under .NET it prints
+item count: 4
+because the setter is not called.
+The item count is 4 because the ctor always creates a non-
+empty list, hence the list grows after the deserialization.
+It appears, that (just a guess) for generic ArrayLists
+attributed with [XmlElement] the patch doesn't work.

More information about the mono-bugs mailing list