Comment 2 for bug 492674

Thanks for the help in understanding this issue. I will try saving an NUnit project as you suggested. It still seems more like a bug than a missing feature to me though. If you still think this is a feature request I won't make a fuss about it. I am just glad you want to implement this, but I also want to help you think about things from a user perspective. Thanks for working on this open source project!

Here is my reasoning on why this seems like a bug, from a user perspective:

The fact that specifying a configuration merely refers to the NUnit project configuration rather than the solution configuration sounds more like an internal implementation detail than an intended external behavior, especially since it is creating the NUnit project in memory and (somewhat) adapting it to the solution.

Looking to the documentation found here http://www.nunit.org/index.php?p=guiCommandLine&r=2.5.2 it makes it seem like you are specifying the .csproj configuration, not an NUnit project configuration. I say that because it does not even refer to the creation of an NUnit project, and even though it does not cover solutions, the lack of covering solutions implies that they work the same way, that is, referencing the configuration for that solution.

From a user standpoint, it definitely seems like you are referring to the solution configuration when use something like "nunit nunit.tests.sln /config:Release"