[Mono-devel-list] Re: FW: Soap Serialization interop

Roei Erez roeie at mainsoft.com
Wed Jun 22 00:54:31 EDT 2005

I have opened a bug as you requested, number 75346.

-----Original Message-----
From: mono-devel-list-bounces at lists.ximian.com
[mailto:mono-devel-list-bounces at lists.ximian.com] On Behalf Of Rafael
Sent: Tuesday, June 21, 2005 4:56 PM
To: Robert Jordan
Cc: mono-devel-list at lists.ximian.com
Subject: Re: [Mono-devel-list] Re: FW: Soap Serialization interop


We fix things in the interop/serialization area as needed and possible when
enough information is given to us...

Can you send the exceptions or more info, on what is different on
collections serialization. It would be very nice if you could fill a bug
case at
with all the details you can gather and a testcase if possible.


On 6/21/05, Robert Jordan <robertj at gmx.net> wrote:
> Roei Erez wrote:
> > I have an issue using mono soap serialization, and I want to know if 
> > it is a bug.
> > The serialization and deserialization of the 'System.Collections' 
> > classes works ok with mono, but is not compatible with .NET, means 
> > that .NET uses other fields for serialization of these objects, and 
> > therefore can not deserialize objects that were serialized by mono.
> > Is this a bug or there was no intention of making it compatible from 
> > the first place?
> The SOAP serialization, like the binary serialization, reflects on 
> then private members of a class. Those members differ between Mono and 
> MSFT .NET because they are highly implementation specific (i.e.
> they might just differ because the Mono team uses another algorithm 
> etc.). Only some basic types share the same member names, and, very
> important: the same meaning.
> These differences/incompatibilities even exist between MSFT's .NET 
> versions.
> SOAP + binary serialization is only intended for short-living objects, 
> like in remoting contexts. Everything else (persisting to 
> disk/database etc.) should only be done with your own lovely designed 
> objects using custom serialization. Those objects already interop 
> between MSFT & Mono, so I don't think the Mono team will ever start to 
> fix this problem.
> Rob
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list

Rafael "Monoman" Teixeira
I'm trying to become a "Rosh Gadol" before my own eyes. 
See http://www.joelonsoftware.com/items/2004/12/06.html for enlightment.
It hurts!
Mono-devel-list mailing list
Mono-devel-list at lists.ximian.com

More information about the Mono-devel-list mailing list