nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

Postponed to 3.0

** Changed in: nunitv2
    Milestone: 2.6.0 => None

** Tags added: console feature gui

** Project changed: nunitv2 => nunit-3.0

-- 
Specifying the solution's configuration specifies the sub-project's configurations instead
https://bugs.launchpad.net/bugs/492674
You received this bug notification because you are a member of NUnit
Developers, which is subscribed to NUnit V2.

Status in NUnit Test Framework: Confirmed

Bug description:
When starting the NUnit GUI from the command line, you can specify a configuration. If you are doing this with a solution instead of an individual project, it does not work correctly. It assumes that all the projects have the same configuration name as the solution configuration. While this is often true, it is possible to have a solution configuration that uses project configurations of a different name.

If you need more detail, this is how I have my project set up in Visual Studio 2008. I use the Configuration Manager under the Build menu to organize my configurations. I have a solution configuration called "Test". Some of the projects under this solution do not even have a configuration called "Test". For these projects I have the "Test" solution configuration using the "Debug" version of those projects. When I load the NUnit GUI using the command line and pass it the location of the solution file and instruct it to use the "Test" configuration, it only loads the projects with a configuration called "Test" and therefore is ignoring the solution configuration settings.