[Mono-devel-list] Problem with MS.NET and Mono with Remoting

Miguel de Icaza miguel at ximian.com
Wed Jul 20 13:01:54 EDT 2005


> > > http://bugzilla.ximian.com/show_bug.cgi?id=75575
> Does someone know if this type of bug will be resolved a day...
> Or help me how to resolve this issue... I don't know where to begin...
> Interoperability with Mono and MS.NET with .NET remoting is crucial for my 
> firm... I think it's crucial for mono too

Some of these bugs can be fixed on a case-by-case basis.  The simple
cases are ones where we need to rename our internal fields to have the
same name as Microsoft.

The hard cases is when the implementations differ and no amount of
renaming our internal fields will help.  

Since your code might add more or less dependencies on remoting as times
goes by to classes that we can not or have not edited to match the
over-the-wire naming this will be a continuous source of problems for

My recommendation if you need a Windows/Linux interop stack is to use
soap web services (which transfers exactly what its asked to transfer,
not serialize the internals of a class) or if you need something faster
you can look at ZeroC.com's Ice library.

Ice works across Windows and Linux, its fast and will give you much more
than remoting does today in addition to interop to other languages.


More information about the Mono-devel-list mailing list