[Mono-bugs] [Bug 79720][Nor] Changed - [PATCH] Runtime should not search loaded assembly when using Assembly.Load

[bugzilla-daemon at 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 gert.driesen at pandora.be.

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

--- shadow/79720	2006-10-22 09:21:52.000000000 -0400
+++ shadow/79720.tmp.4410	2006-10-22 11:49:21.000000000 -0400
@@ -11,13 +11,14 @@
 AssignedTo: mono-bugs at ximian.com                            
 ReportedBy: gert.driesen at pandora.be               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
 URL: 
 Cc: 
-Summary: Runtime should not search loaded assembly when using Assembly.Load
+Summary: [PATCH] Runtime should not search loaded assembly when using Assembly.Load
+BugsThisDependsOn: 76757
 
 Currently when an assembly is loaded using Assembly.Load (AssemblyName) 
 or Assembly.Load (string), the runtime will first search the loaded 
 assemblies to check whether the AssemblyName of one of these matches the 
 specified AssemblyName. This is done is mono_assembly_load_full 
 (assembly.c).
@@ -34,6 +35,32 @@
 
 ------- Additional Comments From gert.driesen at pandora.be  2006-10-22 07:06 -------
 I'll check the MS behavior for this one too.
 
 ------- Additional Comments From kornelpal at gmail.com  2006-10-22 09:21 -------
 I think this is a duplicate of Bug 78464
+
+------- Additional Comments From gert.driesen at pandora.be  2006-10-22 11:49 -------
+I've committed 2 unit test for this change in AppDomainTest.cs (one 
+marked NotWorking for now). 
+
+The Load_Loaded_Multiple test (what's in a name) verifies the 
+behaviour when a given assembly is loaded multiple times through 
+AppDomain.Load (AssemblyName). This test will pass on Mono and 
+MS.NET, before and after my patch (which I'll attach in a sec). 
+
+I'll also attach a small standalone test application that verifies 
+my fix. Running this test application yields the same results on 
+both Mono and MS.NET after applying my patch....
+
+Except for the last test with the separate AppDomain, which is 
+broken on the 2.0 profile after applying my patch.
+
+However, I'm pretty sure that issue is really a(nother) bug that my 
+patch exposes in another part of Mono. 
+
+I reported this regression in the 2.0 profile before:
+http://bugzilla.ximian.com/show_bug.cgi?id=76757
+
+How do you propose to proceed with this ? The 2.0 regression in bug 
+#76757 should definitely get fixed before the patch for this bug is 
+applied.