I have a large-ish Visual Studio 2010 solution (~110 C# projects). One project (let's call it 'A') is a console application that has about 6 dependencies on other projects and some 3rd party assemblies.
If I build project 'A' it builds the dependencies as expected.
If I right-click on project 'A' and choose Debug | Start new instance, it first builds the project, and then proceeds to build a whole lot of other projects too. Watching the Output window, it's like it keeps restarting the build process for each of these other project and their dependencies.
The problem is that the original project 'A' does not depend on these other projects (directly or indirectly) that Visual Studio is building before starting the debugger.
This means that it takes ages before the debugger is launched.
I have customised the .csproj files in some of the other projects but have not customised the 'A' project.
Command-line builds via msbuild all behave normally.
What would be causing Visual Studio to do this?