[Mono-bugs] [Bug 75377][Min] Changed - Cross-AppDomain delegate marshaling 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=75377

--- shadow/75377	2005-06-25 19:09:53.000000000 -0400
+++ shadow/75377.tmp.19352	2005-06-25 19:29:41.000000000 -0400
@@ -113,6 +113,31 @@
 
 It's not all that unreasonable to say "you must take care in handling
 the intptrs so that you don't call into another AD".
 
 Anyways, we should see what msft has to say about this. Can you post
 the bug reference on msdn.
+
+------- Additional Comments From kornelpal at hotmail.com  2005-06-25 19:29 -------
+Reference: 
+http://lab.msdn.microsoft.com/productfeedback/viewfeedback.aspx?
+feedbackid=3e46264b-6cb4-431f-9726-c8d3dbd55927
+
+It can't be the expected result to execute instance methods in a 
+different AppDomain than they belong to. There are two resonable 
+solutions: disallow cross AppDomain delegate marshaling or execute 
+methods in the right AppDomain. The current behaviour is a nonsense.
+
+>"fixing" this bug wouldn't make us run real life programs any
+>better.
+
+I think that delegate marshaling is a real life scenario. Unmanaged 
+code is portable at source code level and there are situations when 
+it is needed. And when you pass marshaled delegates to unmanaged 
+code that code can pass back marshaled delegates to managed code 
+even that are in different AppDomain.
+
+>It's not all that unreasonable to say "you must take care in
+>handling the intptrs so that you don't call into another AD".
+
+As you get and IntPtr to an unmanaged funtion it's the runtimes 
+responsibility to take care of AppDomain as you cannot.