I have a solution containing both WinForms and asp.net projects. There is nothing wrong with this. However, when I set a configuration that runs only a single WinForms project where all of the asp.net projects aren’t even marked for build and start debugging I still get an asp.net development server per asp.net project – that’s two development servers for me. Or better, that’s two useless, memory and CPU cycles wasting development servers running in background.
One would think that this is some sort of bug, so did I. But hey, no, this is by design:
Isn’t that generous from Visual Studio 2005 – to give me more than I asked for?
Anyway, I’ve reopened bug report: