[Mono-bugs] [Bug 66060][Min] Changed - AppDomain.AssemblyResolve event not emitted

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Thu, 16 Sep 2004 02:49:31 -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 peter@newton.cx.


--- shadow/66060	2004-09-16 01:54:35.000000000 -0400
+++ shadow/66060.tmp.29268	2004-09-16 02:49:31.000000000 -0400
@@ -54,6 +54,21 @@
 System.Reflection.Assembly:Load (string)
 in <0x00056> DemoApp:Main (string[])
 May be it was a bug in 1.0, but i rememmber making this work long time
+------- Additional Comments From peter@newton.cx  2004-09-16 02:49 -------
+Oops, I just messed up. There is a second part to this, however; I'm
+not sure if it's a bug. I have code that does this:
+Assembly foo = Assembly.Load ("blah");
+for (AssemblyName name in foo.GetReferencedAssemblies ())
+    dostuff (name);
+If foo loads successfully, but one of its referenced assemblies can't
+be found, should AssemblyResolve still be emitted? It isn't right now;
+instead there's just an unconditional exception (icall.c:3248).