(a) Give me a way to turn off the permanent background compilation.
(b) Implement some sort of smart compilation. When I have a solution consisting of 1 EXE and 9 DLLs I see no reason whatsoever that all 10 parts are compiled, when all I did was change one line of code in the EXE-Project.
Heiko

And two more on VS.NET in General
TonyVal
Project A depends on Project B
I hit "Build/Build Project A" and both projects are listed in the output screen as having been built. Project B doesn't actually get built but it is still listed in the output and still takes up some time.
scarleton
VC6 (and VC7 i believe) give you the option of building:
- Project
- Project and dependencies
- Full solution
All solutions should have these 3 options too.
shaggy073077
Jowins
As for smart compilation--I'm not seeing this. On the Build menu, you always have the option of either building the entire solution, or building the project you're currently in. I don't need to build the 9 DLLs if I'm working on a piece of the one EXE. Is there something you're looking for that isn't this behavior
agilegroup
I am under the impression that the background compilation is slowing my computer down *big time*. I mean "devenv" grabs about 96% CPU Power for 5 to 10 Minutes after startup. And whenn I edit large chunks of code, i.e. produce a large number of syntax error in a short period of time (renaming variables, changing interfaces, whatever) I can't even scrool smoothly any more.
We have a sln of 10 projects and about 150 classes.
Heiko