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

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Wed, 26 May 2004 16:00:05 -0400 (EDT)


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-05-26 14:05:13.000000000 -0400
+++ shadow/58608.tmp.18120	2004-05-26 16:00:05.000000000 -0400
@@ -699,6 +699,22 @@
 
 
 ---------------------------------------------------------------------
 -----
 Thanks
 
+
+------- Additional Comments From lluis@ximian.com  2004-05-26 16:00 -------
+I've build 4 assemblies with the following files:
+
+1) RemotingClient.cs
+2) RemotingServer.cs
+3) RemoteObject.cs
+4) XferObjectSimple.cs, XferObjectBase.cs, XferObject.cs, AssemblyInfo.cs
+
+Only the 4th assembly is signed.
+
+I've tried the test case and it works for me. Both .NET client vs Mono
+server, and .NET server vs Mono client. Maybe there was an assembly
+loading bug in the runtime that has been fixed. However, I'll leave
+the bug open until you have the chance to try Beta2 or a CVS snapshot.
+