[Mono-bugs] [Bug 57602][Wis] Changed - Mono major assembly loader issues

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Mon, 26 Apr 2004 13:23:34 -0400 (EDT)

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 gert.driesen@pandora.be.


--- shadow/57602	2004-04-26 12:29:23.000000000 -0400
+++ shadow/57602.tmp.1220	2004-04-26 13:23:34.000000000 -0400
@@ -208,6 +208,26 @@
 What you really want to do is hook into AppDomain.AssemblyResolve. 
 You can redirect the reference to the assembly here. That should work 
 just fine. This is going to be alot faster on both runtimes, and is 
 alot less messy.
 Am thinking this is a wishlist issue still...
+------- Additional Comments From gert.driesen@pandora.be  2004-04-26 13:23 -------
+Not sure if this is documented some place, so it might indeed by a 
+side effect of the MS implementation, but I thought Mono was about 
+compatiblity too ...  This wouldn't be the first case were the actual 
+implementation differs from the docs, and in about all cases Mono has 
+chosen to match the implementation ... but well ...
+I don't think consuming the AppDomain.AssemblyResolve event would've 
+been an option as assembly references for the default AppDomain are 
+resolved before you can even attach an eventhandler to consume this 
+event (please correct me if I'm wrong).
+Even if this is possible, then all task developers would have to know 
+about this and always attach an eventhandler to newly created 
+AppDomain's (which is sometimes necessary to avoid loading assemblies 
+in the main appdomain). 
+The separate appdomain for the NAnt.Core is something that was 
+already in place, so I chose not to touch this ...