[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 16:51: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 bmaurer@users.sf.net.


--- shadow/57602	2004-04-26 16:46:41.000000000 -0400
+++ shadow/57602.tmp.5304	2004-04-26 16:51:34.000000000 -0400
@@ -12,13 +12,12 @@
 ReportedBy: gert.driesen@pandora.be               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
 Summary: Mono major assembly loader issues
 BugsThisDependsOn: 57612
-OtherBugsDependingOnThis: 52813
 I've stumbed upon the following major differences between the MS.NET and 
 Mono assembly loader :
 1) Mono immediately resolves the whole tree of assembly references 
 (meaning if loading an assembly "a", not only the assemblies referenced 
@@ -283,6 +282,16 @@
 and got a WONTFIX. 
 Is there any chance that it can be fixed along with the early-loading
 issue? This is really important in chicken-egg situations like the one
 I described and looks similar to what I've reported.
+------- Additional Comments From bmaurer@users.sf.net  2004-04-26 16:51 -------
+On the compiler issue, it *might* work after #1 is finished, but no
+promises. The problem is that we load types using System.Reflection,
+even if they are not directly referenced. So, if something caused a
+dll to be loaded that did not exist, you might get an error.
+The compiler issue is completely seperate form this bug. If we want to
+continue discuession on it, lets open another bug.