[Mono-bugs] [Bug 76757][Nor] Changed - new AppDomains inherit current loaded assemblies

[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 brian at fluggo.com.

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

--- shadow/76757	2006-06-14 19:42:07.000000000 -0400
+++ shadow/76757.tmp.20989	2006-06-14 21:03:08.000000000 -0400
@@ -1,12 +1,12 @@
 Bug#: 76757
 Product: Mono: Runtime
 Version: 1.1
 OS: unknown
 OS Details: 
-Status: NEW   
+Status: ASSIGNED   
 Resolution: 
 Severity: Unknown
 Priority: Normal
 Component: misc
 AssignedTo: mono-bugs at ximian.com                            
 ReportedBy: spigaz at gmail.com               
@@ -432,6 +432,28 @@
 
 ------- Additional Comments From gonzalo at ximian.com  2006-05-01 14:15 -------
 I'm not fixing this.
 
 ------- Additional Comments From kornelpal at gmail.com  2006-06-14 19:42 -------
 *** Bug 78648 has been marked as a duplicate of this bug. ***
+
+------- Additional Comments From brian at fluggo.com  2006-06-14 21:03 -------
+Well, if this is the bug we're working with, then let me tell you what
+I see.
+
+First, I have a patch that will create an AppDomain properly. It
+eliminates the block of code in mono/metadata/appdomain.c that copies
+all known assemblies into the new one and instead just adds the
+corlib. That's no problem, but it does make a second painfully obvious.
+
+Second, the transparent proxy used to marshal AppDomains is no good.
+There's whole crack CrossAppDomain remoting stack that attempts to do
+as little work as possible moving calls and data between AppDomains.
+As a result, if the assembly containing the target of your
+CrossAppDomainDelegate is not already loaded in the target domain,
+your call will fail. (In fact, I bet I could make it fail without the
+first patch. Create the AppDomain, then dynamically load an assembly
+that performs the AppDomain.DoCallBack call. Zing!)
+
+I am still investigating a fix, but the simplest solution to me seems
+to be to remove the whole CAD stack and use a pure binary serializer.
+More news as it develops.