[Mono-dev] SPAM-LOW: AppDomainSetup.ConfigurationFile
charlie at nunit.com
Mon Nov 3 13:50:18 EST 2008
Are you using a full path? I have the following comment
and code in NUnit:
// Note: Mono needs full path to config file...
setup.ConfigurationFile = Path.Combine( appBase, configFile );
I'm not sure if this is still true - the code has been
there for a while. I think I filed a bug, since .NET works
with just the file name, but I can't find it.
> -----Original Message-----
> From: mono-devel-list-bounces at lists.ximian.com
> [mailto:mono-devel-list-bounces at lists.ximian.com] On Behalf
> Of Jacob Gladish
> Sent: Monday, November 03, 2008 10:25 AM
> To: mono-devel
> Subject: SPAM-LOW: [Mono-dev] AppDomainSetup.ConfigurationFile
> Can anyone confirm whether this is still broken? I'm trying
> to start an assembly in another AppDomain with an alternate
> configuration file and it does not appear to be working. I'm
> trying to figure out whether this is broken in the framework.
> I'm using 1.9.
> With that said, my real problem is that I'd like to be able
> to run my application from NFS and be able to use varying app
> configs. Has anyone found a good solution for this? My
> approach is to have a -config option whereby I simply create
> a new AppDomain, specify the ConfigurationFile from the
> command line, and execute the current assembly in the new
> domain. This currently is not working because of the
> aforementioned problem.
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
More information about the Mono-devel-list