[Mono-bugs] [Bug 74295][Nor] Changed - Mono and MS .Net remoting - type encodings don't agree
Fri, 1 Apr 2005 20:34:01 -0500 (EST)
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 firstname.lastname@example.org.
--- shadow/74295 2005-04-01 12:17:23.000000000 -0500
+++ shadow/74295.tmp.15856 2005-04-01 20:34:01.000000000 -0500
@@ -180,6 +180,24 @@
*** Bug 74108 has been marked as a duplicate of this bug. ***
------- Additional Comments From email@example.com 2005-04-01 12:17 -------
Created an attachment (id=14818)
+------- Additional Comments From firstname.lastname@example.org 2005-04-01 20:34 -------
+Um, this is what I get for reading Microsoft docs (well, stands
+to reason that they have problems with case)...
+The original patch was slightly broken - it's supposed to be
+xsd:boolean, not xsd:Boolean. Oddly enough, MS .Net was okay
+accepting xsd:Boolean as a type, but it writes out xsd:boolean,
+so Mono still didn't understand. I suppose that's a new aspect
+to the bug - there's basically the same problem in ArrayLists
+for booleans as for doubles.
+Speaking of ArrayList problems, there are several other types
+that MS .Net serializes in ArrayLists as XSD types that Mono
+doesn't recognize - so I added those to the patch as well.
+They are: uint, ushort, ulong, and sbyte. (I'm guessing the
+problems with ArrayList will also show up anywhere the type is
+ambiguous - e.g., other containers - but that's just a guess.)