[Mono-bugs] [Bug 65903][Nor] Changed - appdomains assembly resolution is being leaked to other appdomains

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Thu, 16 Sep 2004 16:35:01 -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 ddulai@bloomberg.net.


--- shadow/65903	2004-09-16 16:29:25.000000000 -0400
+++ shadow/65903.tmp.13247	2004-09-16 16:35:01.000000000 -0400
@@ -126,6 +126,21 @@
 /out to mcs:
 mcs /target:library /out:foo1.dll foo.cs
 mcs /target:library /out:foo2.dll foo.cs
 This way, the two assemblies will have a different assembly name.
+------- Additional Comments From ddulai@bloomberg.net  2004-09-16 16:35 -------
+the problem is that they actually have the same assembly names. what 
+im doing is creating an application server that can load an assembly 
+into an appdomain. and then when given the command to do so, can load 
+a new assembly into a different app domain. the new assembly may be  
+rev2 of the rev1 assembly running in the first appdomain. i need both 
+rev1 and rev2 both running in the same physical process (in diff 
+at first i was unsure if this was possible, but i have code working 
+with the msft implementation and its working great!
+will the fix work even for the case above in 1.0.2 or the most recent