[Mono-bugs] [Bug 78464][Nor] Changed - Assembly.Location is
zero-length string if assembly was first loaded from byte array
bugzilla-daemon at bugzilla.ximian.com
bugzilla-daemon at bugzilla.ximian.com
Sat May 20 09:23:49 EDT 2006
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 kornelpal at gmail.com.
http://bugzilla.ximian.com/show_bug.cgi?id=78464
--- shadow/78464 2006-05-20 07:46:17.000000000 -0400
+++ shadow/78464.tmp.2816 2006-05-20 09:23:49.000000000 -0400
@@ -40,6 +40,19 @@
------- Additional Comments From vargaz at gmail.com 2006-05-20 07:46 -------
An assembly cannot be loaded twice into the same appdomain. The second
attempt will return the already loaded assembly. Does this work under
MS.NET ?
+
+------- Additional Comments From kornelpal at gmail.com 2006-05-20 09:23 -------
+The test case works without exceptions and no Console.WriteLine
+("Failure #x") is called.
+
+But note that MS.NET and Mono assembly loading and caching is too
+different. I think some fundamental changes are necessary.
+
+But I don't really know how Mono decides whether load a new instance
+or use a cached one. Could you please summarize this process?
+
+If I understand how Mono works I'll try to write some test case that
+point out the differences.
More information about the mono-bugs
mailing list