[Mono-bugs] [Bug 58608][Nor] Changed - Sending a Signed Assembly using Remoting causes a Serialization Exception

[bugzilla-daemon@bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by lluis@ximian.com.

http://bugzilla.ximian.com/show_bug.cgi?id=58608

--- shadow/58608	2004-06-08 21:29:55.000000000 -0400
+++ shadow/58608.tmp.18758	2004-06-10 13:36:02.000000000 -0400
@@ -912,6 +912,25 @@
    at RemotingTest.RemotingClient.Main() in 
 c:\amadeus\dev\mono\assmblytest\asse
 mblytest\remotingclient\remotingclient.cs:line 52
 ###################################
 Done. Press Enter to exit.
 
+
+------- Additional Comments From lluis@ximian.com  2004-06-10 13:36 -------
+Ok, I think I found the issue. This is not a bug. The problem is the
+following declaration:
+
+[assembly: AssemblyVersion("1.0.*")]
+
+It means that every time you compile the assembly, it will get a new
+version number. If you compile the xfer assembly both in Windows and
+in Linux, you'll get the same assembly, but with two different
+versions. Even if you use the same key, the strong name will be
+different. And that's why the system can't find the assembly, because
+the copy it has has a different strong name.
+
+To fix this just remove the "*" and add a complete version number. Or
+compile the assembly only once and copy the same over all systems.
+
+Can you please confirm that this is the problem? 
+