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

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Tue Nov 22 02:23:15 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 kornelpal at hotmail.com.


--- shadow/76757	2005-11-21 20:03:58.000000000 -0500
+++ shadow/76757.tmp.1662	2005-11-22 02:23:15.000000000 -0500
@@ -235,6 +235,28 @@
 Fixing this should encompass fixing anything that might make ASP.NET
 and xsp fail.
 Keeping ASP.NET and xsp working is of higher importance than this
 corner case.
+------- Additional Comments From kornelpal at hotmail.com  2005-11-22 02:23 -------
+I noticed that we are talking about this bug for a long time but 
+haven't evaluated it's real impact yet. I compiled mono with the 
+patch from Jb Evain applied. I noticed that all my attached test 
+cases are working as expected.
+Note that however I wasn't able to use xsp as it seemed not to 
+listen on any port, but I got the same result on MS.NET so this 
+seems to be a bug in xsp rather than mono that should be fixed.
+MS.NET was missing xsp.exe from the bin directory of the new 
+AppDomain while mono was able to load it that seems to be a mono bug.
+xsp should run under MS.NET with all of it's dependent assemblies 
+installed to GAC. But it should not use methods found in xsp.exe in 
+the new AppDomain unless it loads xsp.exe to the new AppDomain 
+explicitly otherwise this will be another xsp bug that will preven 
+mono runtime being patched.
+As a conclusion I think fixing this bug has no inpact on mono but 
+xsp has bugs that should be fixed by making it able to run on MS.NET.

More information about the mono-bugs mailing list