[Mono-devel-list] un-interoperatible classes .NET -> Mono remoting

Lluis Sanchez lluis at ximian.com
Tue Sep 28 07:19:45 EDT 2004

On dt, 2004-09-28 at 03:52 -0700, Aleksandar Dezelin wrote:
> Lluis Sanchez wrote:
> >Only objects whose internal structure is identical in MS.NET and Mono
> >(i.e. they have the same private fields with the same names) are
> >interoperable. The reason is that remoting sends a full copy of the
> >object and if the receiver expects a different structure for a type it
> >will fail. Classes in System.Collections have been gradually modified to
> >match those in MS.NET. Other classes may fail.
> >
> >Lluis.
> >
> Then System.Collections and it's classes including Hashtable are
> interoperable? Is there any kind of list of non-interoperable classes?

No, there isn't such a list. Remoting interoperability between different
CLR implementations is not guaranteed. Some classes that may be
interoperable nowadays, may change its internal structure in the future
and break that compatibility. For example, if you find that the class
CultureInfo is not compatible with MS.NET, we can change it to make it
compatible, but then we will break interoperability with old mono

If interoperability is important to you, you should consider using web
services instead of remoting.


> Regards
> Aleksandar Dezelin

More information about the Mono-devel-list mailing list