OK whats happening is that we pass a config file to our test assemblies. This config file will have the default set to 1.0 causing problems when the test initialises.
There is currently no easy way of passing the -k value thru to the tests as they are standalone test assemblies that could be run from the NUnitConsole rather than the NUnit task.


I've written a quick hack to generate a new config file in the temp folder with the default framework set to what was passed in -k, and then passes that config to the tests. This works but its not the 'right' solution because its in the NUnitTask.cs and will try and run for every test task - not just the tests for nant.

This will do in a pinch as it will solve the problem without too much overhead, but I'm haveing a look at alternatives.

Ian

----- Original Message ----- From: "Ian MacLean" <[EMAIL PROTECTED]>
To: "David Reed" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, September 12, 2003 5:24 AM
Subject: Re: [nant-dev] Framework 1.0 dependency in ConsoleStub.cs





David Reed wrote:



Thanks for the hint on where to look!  I had to change two settings in
NAnt.Console.exe.config as follows to get it to work:

<nantsettings defaultframework="net-1.1"
taskpath=".\optional">






I've found out why the -k option doesn't propogate to the tests and I'm working on a fix. However the above workaround obviously does the job.



What's causing this ??


Gert







------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers

Reply via email to