[Mono-bugs] [Bug 67727][Nor] Changed - same assembly cant be loaded twice
Thu, 7 Oct 2004 10:20:42 -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 firstname.lastname@example.org.
--- shadow/67727 2004-10-07 10:20:20.000000000 -0400
+++ shadow/67727.tmp.5675 2004-10-07 10:20:42.000000000 -0400
@@ -46,6 +46,36 @@
globally, but should be checked within the context
of an AppDomain.
Bug #65903 is similar, but had additional stuff
that was fixed already. It also contains code on
how to reproduce this.
+------- Additional Comments From email@example.com 2004-10-07 10:20 -------
+miguel has asked me to add the following comments:
+lets say we have an app developer that creates application 'foo'.
+we can move foo.dll into foo-beta.dll and have the appserver load it
+into an app domain on the fly when a user comes to the appserver
+asking for 'foo', and is privledged to see beta code.
+but for other users, beta is no good, so they would need to load a
+previously created foo-prod.dll, which is also application 'foo'. most
+likely it is last months beta, just renamed to foo-prod.dll and its
+privledging changed in our privledging database.
+The point is that the name should not be the key for the assembly in a
+global scope. Everything assembly related should be scoped within an
+AppDomain. I go through great trouble to not touch anything in the
+master AppDomain that may cause foo-*.dll to get loaded into it.
+A good analogy would be this:
+OS process -- DLL
+ AppDomain -- Assembly
+This is pretty well explained on MSDN in their 'Using Application
+Domains' > section in the .NET Framework Developers Guide: