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

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Mon Nov 21 08:19:49 EST 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 kornelpal at hotmail.com.


--- shadow/76757	2005-11-21 07:23:28.000000000 -0500
+++ shadow/76757.tmp.23396	2005-11-21 08:19:49.000000000 -0500
@@ -157,6 +157,30 @@
 Which fixes this bug:
+------- Additional Comments From kornelpal at hotmail.com  2005-11-21 08:19 -------
+The fix for Bug 65665 is quite incorrect. It is no special case. The 
+runtime has to load the appropriate mscorlib.dll version into the 
+new AppDomain. Nothing else should be done. Then if you try to 
+execute AppDomain.DoCallBack for example the delegate has to be 
+serialized then desereialized in the new AppDomain. This means that 
+it's the responsibility of the remoting infrastructure to load 
+required assemblies to the new AppDomain. Furthermore it means that 
+AppDomain.DoCallBack will fail if the required assembly cannot be 
+loaded to the new AddDomain using standard assembly lookup 
+mechanism. In addition this may result in the load of a different 
+binary for the same AssemblyName to the new AppDomain.
+This is the expected behavior. For some examples please try the 
+previously attached tests.
+Note that however that MS.NET runtime supports domain-neutral 
+assembly loading depending on configuration:
+But even when using domain-neutral assembly loading it will affect 
+only assembly resolving rather than result in preloaded assemblies.

More information about the mono-bugs mailing list