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

[bugzilla-daemon@bugzilla.ximian.com]

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 gonzalo@ximian.com.

http://bugzilla.ximian.com/show_bug.cgi?id=66060

--- shadow/66060	2004-09-15 20:45:25.000000000 -0400
+++ shadow/66060.tmp.28823	2004-09-16 01:54:35.000000000 -0400
@@ -1,14 +1,14 @@
 Bug#: 66060
 Product: Mono: Class Libraries
 Version: unspecified
-OS: 
+OS: unknown
 OS Details: 
-Status: NEW   
-Resolution: 
-Severity: 
+Status: RESOLVED   
+Resolution: NOTABUG
+Severity: Unknown
 Priority: Minor
 Component: CORLIB
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: peter@newton.cx               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
@@ -29,6 +29,31 @@
 before an exception is thrown, but no message appears.
 
 ------- Additional Comments From peter@newton.cx  2004-09-15 20:45 -------
 Created an attachment (id=10748)
 Demonstration of problem
 
+
+------- Additional Comments From gonzalo@ximian.com  2004-09-16 01:54 -------
+It works here. And I tried CVS HEAD and CVS 1.0 branches:
+
+-----------------------------------
+gonzalo@pm:~/go-mono$ mono ar.exe
+Trying to resolve nonexistentassembly
+ 
+Unhandled Exception: System.IO.FileNotFoundException: File
+'nonexistentassembly' not found.
+in <0xc7b168ae> (wrapper managed-to-native)
+System.AppDomain:LoadAssembly (string,System.Security.Policy.Evidence)
+in <0x00004> (wrapper managed-to-native) System.AppDomain:LoadAssembly
+(string,System.Security.Policy.Evidence)
+in <0x0006a> (wrapper remoting-invoke-with-check)
+System.AppDomain:LoadAssembly (string,System.Security.Policy.Evidence)
+in <0x0003f> System.AppDomain:Load (string)
+in <0x00058> (wrapper remoting-invoke-with-check)
+System.AppDomain:Load (string)in <0x0001c>
+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
+ago.