Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report for Bug 5694 on
GitHub or Developer Community if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Created attachment 2072 [details]
Test case with outputs
In the test case there is a solution with three projects - a common type library (BugTest), a remoting client application (BugTest.Client) and a server application (BugTest.Server). The client application recieves a proxy to an object which implements interface ITest. This object is an instance of class TestImpl which is known to both server and client (it is defined in the common library). When the client calls a method on the proxy through interface ITest, the remoting message sent to the server refers to the method that is the implementation of the ITest's method in TestImpl, rather than referring to the ITest's method itself.
This problem becomes serious when the server runs on .NET, the client on Mono and the ITest's method is implemented explicitly in TestImpl. In this case, .NET recognizes the method as private and therefore throws a RemotingException. When you run the client application on .NET, you can see that in the message it refers to the method defined in ITest, not to the TestImpl's implementation.
In the attachment, I also included outputs of client and server when run in different evironments ("mono->net_client.out", for example, is the output of client where client ran on Mono, server ran on .NET).
Mono details: v2.10.x on Linux
.NET Framework details: v4.0 on Windows XP
The server application accepts one command-line argument - the port to listen on. The client application accepts two arguments - the address and port of the server.
I believe that Mono should generate the same messages as .NET in these cases in order to prevent problems with .NET servers.