Okay, here's what I've done so far:

I've got a VS.NET VB.NET solution with four projects:  a Windows App, a
Forms Library, a Data Access layer DLL, and a BLL dll.  To this solution,
I've added a C# Class Library to house all of my NUnit Tests.  

Now, sometimes I want to be able to debug the Windows App, sometimes I want
to be able to run my NUnit tests, and sometimes I want to compile a
release-quality end product (minus the NUnit Test Bed), so I've add an
additional custom configuration called NUnit which builds all five projects
in debug mode.  My debug configuration doesn't build the NUnit library but
builds all the other projects in debug mode.  And my release configuration
builds the four projects in release mode.  This works fine, except for the
following.

What I want to do:

I want to be able to specify a different startup project for different
configurations.  For my Debug and Release configurations, I want the startup
project to be the Windows App, but for the NUnit configuration I want the
startup project to be the NUnit Class Library which triggers the
NUnit-Gui.exe.  It looks like you can only specify one startup project for
each solution.  

Is there a way around this?  

Thanks very much,

TheManFromSQL