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

Jason King jason.king at profox.co.uk
Tue Sep 28 07:02:04 EDT 2004

Hello Aleksandar
As a useful tool for examing MS.NET classes, you could try Reflector,
available here: http://www.aisto.com/roeder/dotnet/

This should allow you to inspect the classes and compare with Mono
libraries / source code to see those definitions that are different.

Hope this helps,

Jason King
Co-Author, "Cross-Platform .NET Development: Using Mono, Portable.NET,
and Microsoft .NET" 
(Apress, 2004, ISBN: 1-59059-330-8)

-----Original Message-----
From: mono-devel-list-admin at lists.ximian.com
[mailto:mono-devel-list-admin at lists.ximian.com] On Behalf Of Aleksandar
Sent: 28 September 2004 11:52
To: Mono-devel-list
Subject: Re: [Mono-devel-list] un-interoperatible classes .NET -> Mono

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.

Then System.Collections and it's classes including Hashtable are
interoperable? Is there any kind of list of non-interoperable classes?

Aleksandar Dezelin
  Aleksandar Dezelin
  dezelin32 at fastmail.fm

Mono-devel-list mailing list
Mono-devel-list at lists.ximian.com

More information about the Mono-devel-list mailing list