logo       

2.2.3 - problem w/ config file name: msg#00004

windows.dotnet.nunit.devel

Subject: 2.2.3 - problem w/ config file name

Hi,

I've got a project named MyProject. I've got two configurations I might want to run:

<NUnitProject>
<Settings activeconfig="MyProject.local" />
<Config name="MyProject.remote" configfile="MyProject.dll.config" binpathtype="Auto">
<assembly path="bin\Debug\MyProject.dll" />
</Config>
<Config name="MyProject.local" configfile="MyProject.dll.local.config" binpathtype="Auto">
<assembly path="bin\Debug\MyProject.dll" />
</Config>
</NUnitProject>

Note that in the local configuration (MyProject.local), the configfile is named "MyProject.dll.local.config". For some reason, NUnit fails to find this config file. However, if I rename it "MyProject.local.config" (both the file and the reference to it), NUnit does find the file.

This is new behavior as of NUnit 2.2.3 (as I was using both config files w/ some success w/ NUnit 2.2.2).

Cheers,
David


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click


<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise