[Mono-bugs] [Bug 75377][Min] Changed - Cross-AppDomain delegate marshaling bug

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Tue Jun 28 12:42:10 EDT 2005

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 bmaurer at users.sf.net.


--- shadow/75377	2005-06-25 21:02:30.000000000 -0400
+++ shadow/75377.tmp.5107	2005-06-28 12:42:10.000000000 -0400
@@ -156,6 +156,18 @@
 When I run the app I get the result that the object has the same 
 static and instance identifiers in New Domain as in Default Domain. 
 But in New Domain static constructor should be executed that 
 generates a different static identifier.
 Please try the code and share the results.
+------- Additional Comments From bmaurer at users.sf.net  2005-06-28 12:42 -------
+"It is indeed incorrect for objects to be accessible to an appdomain
+other than the one which created them. Marshaling delegates to native
+and back again into another appdomain sidestepped the normal
+protections in place to prevent this. The final product will not allow
+this (a NotSupportedException will be thrown upon an attempt to
+marshal back into the wrong domain -- it's illegal to do this for any
+delegate via marshalling, regardless of whether the target type is
+serializble or MarshalByRef)."
+So, it seems that we need to implement that behavior.

More information about the mono-bugs mailing list