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 PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=80934 --- shadow/80934 2007-02-24 10:03:42.000000000 -0500 +++ shadow/80934.tmp.16877 2007-02-24 14:33:40.000000000 -0500 @@ -62,6 +62,21 @@ The ConfigurationFile_RelativeToApplicationBase test you added to AppDomainTest.cs also fails because of this. A workaround would be to add an internal property in AppDomainSetup which can be be used to access the raw configuration file value (without the ApplicationBase check). + +------- Additional Comments From [EMAIL PROTECTED] 2007-02-24 14:33 ------- +I'm very sorry about that! I added the +ConfigurationFile_RelativeToApplicationBase test to catch exactly +this. I'll upload a new patch with this fixed. + +I've added the following check before the ConfigurationFile property +is used for the first time: + +if (info.ApplicationBase == null) + info.ApplicationBase = def.SetupInformation.ApplicationBase; + +Do you think it makes sense to set the default app base here rather +than in the native 'createDomain' code? At the very least we would +need to establish what the app base will be at this point. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
