[Mono-bugs] [Bug 65903][Nor] Changed - appdomains assembly resolution is being leaked to other appdomains
Thu, 16 Sep 2004 16:29:26 -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 email@example.com.
--- shadow/65903 2004-09-16 00:30:56.000000000 -0400
+++ shadow/65903.tmp.13070 2004-09-16 16:29:25.000000000 -0400
@@ -110,6 +110,22 @@
i upgraded to mono 1.0.1 built from src on linux
(diff pointers complaining from free(), but everything else is the
+------- Additional Comments From firstname.lastname@example.org 2004-09-16 16:29 -------
+The free() etc problems are fixed in CVS, but not in 1.0.1.
+As for the general problem, I assume you made the second assembly
+by copying the original assembly to a new file name. This _does_ not
+create another assembly, the identify of the second assembly will be
+the same as the first, so when the runtime loads the second assembly,
+it discovers that it is the same as the first, so it discards it, and
+uses the first one. The correct way to do this is by specifying
+/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.