[Mono-bugs] [Bug 75378][Nor] Changed - Cross-AppDomain delegate remoting bug

[bugzilla-daemon at 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 kornelpal at hotmail.com.

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

--- shadow/75378	2005-06-25 19:10:24.000000000 -0400
+++ shadow/75378.tmp.18870	2005-06-25 19:16:36.000000000 -0400
@@ -1,13 +1,13 @@
 Bug#: 75378
 Product: Mono: Runtime
 Version: unspecified
 OS: other
 OS Details: 
-Status: RESOLVED   
-Resolution: NOTABUG
+Status: REOPENED   
+Resolution: 
 Severity: Unknown
 Priority: Normal
 Component: remoting
 AssignedTo: mono-bugs at ximian.com                            
 ReportedBy: kornelpal at hotmail.com               
 QAContact: mono-bugs at ximian.com
@@ -65,6 +65,41 @@
 
 ------- Additional Comments From bmaurer at users.sf.net  2005-06-25 18:33 -------
 ^^^^^^^^^
 
 ------- Additional Comments From bmaurer at users.sf.net  2005-06-25 19:10 -------
 Please don't reopen without a reason.
+
+------- Additional Comments From kornelpal at hotmail.com  2005-06-25 19:16 -------
+I reopened the bug to add more comments but you closed the bug again 
+in 37 minutes.:)
+
+The behaviour is a bit different (no ArgumentException for GCHandles 
+for example) in MS.NET 2.0 but the bug is the same [Serializable] 
+objects are not treated as expected.
+
+The article you referenced is correct because delegates are 
+marshaled by value (serialized) and method invokes are proxied 
+through AppDomain for MarshalByRef objects but [Serializable] 
+targets should be serialized according the rules of remoting.
+
+And I'm sure that they are not serialized because static fields are 
+never remoted and the result is the same (object is executed in a 
+different AppDomain than it was created and belongs to) when I use 
+[NonSerialized] private fields.
+
+This should never happen. Target has to be serialized and a new 
+instance created in the other AppDomain.
+
+I reported this bug to MS as well but this is a bug regardless of 
+MS.NET.
+
+You can never convience me of remoting objects just by executing 
+their methods in a different AppDomain they belong to is correct.
+
+There are two types of remoting:
+by-ref using proxies but the code is executed in the original 
+AppDomain
+by-val using serialization in this case a new instance is created 
+that is independent of the original one
+
+There is no "in place" remoting across AppDomains.