[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 12:29:23 -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 bmaurer@users.sf.net.


--- shadow/57602	2004-04-26 11:45:23.000000000 -0400
+++ shadow/57602.tmp.551	2004-04-26 12:29:23.000000000 -0400
@@ -195,6 +195,19 @@
 assembly does not reference it), meaning it has to be in the private 
 path from the start. Making it impossible to use a framework-specific 
 version of the log4net assembly.
 But as you've said, there's also a performance penalty for 
 immediately resolving the completely assembly dependency tree.
+------- Additional Comments From bmaurer@users.sf.net  2004-04-26 12:29 -------
+Is there somewhere in the MS docs that talks about this? The behavior 
+may very well be a side effect of their impl. The method you have is, 
+at best, obscure. Also, by loading in a seperate app domain, you are 
+going to kill perf.
+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...