[Mono-bugs] [Bug 76757][Nor] Changed - new AppDomains inherit current loaded assemblies

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Wed Nov 23 20:15:03 EST 2005

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 robertj at gmx.net.


--- shadow/76757	2005-11-23 15:32:56.000000000 -0500
+++ shadow/76757.tmp.26889	2005-11-23 20:15:03.000000000 -0500
@@ -325,6 +325,31 @@
 directory of MyApplication.exe you can see the result when runtime 
 is able to load MyClassLibrary.dll.
 I see anything in Mono runtime that would break if the patch 
 proposed by Jb Evain were applied. Do we have any reason not to 
 apply this patch?
+------- Additional Comments From robertj at gmx.net  2005-11-23 20:15 -------
+> As I see, currently the created new domains require xsp.exe. When 
+> running on MS.NET I had to copy xsp.exe to the bin directory of the 
+> web application to make the runtime able to find it. Otherwise it 
+> throws an excetption. (If I'm wrong please let me know but this is 
+> what I experienced.)
+This is how hosting is implemented by ASP.NET
+on both runtimes: when a new ASP.NET application is
+about to be created with ApplicationHost.CreateApplicationHost,
+ASP.NET creates a new appdomain and sets the PrivateBinPath
+to the "bin" folder of the physical directory.
+The caller cannot control this step.
+Since the xsp assembly doesn't contain the application
+hosts (Mono.WebServer contains them), it's not needed
+to be copied into "bin", so xsp is totally correctly
+If the patch would be applied, the only necessary "fix"
+for xsp would be to install Mono.WebServer into the GAC.

More information about the mono-bugs mailing list