Compilation responsivness and enhancement
C# and VB.NET compilers are blazingly fast! However, on RebuildAll scenarios, the user experience could be (easily) enhanced if:
1) The progress bar would show accurately the RebuildAll progression.
2) If before compilation, VS could warn/break if one or several target DLLs WndHandle are currently hold by some processes, and which process hold which handle (the process explorer way)
3) RebuildAll doesn't try to recompile DLLs relying on DLLs that didn't compile successfully.
Now it is almost impossible to navigate files or do anything else during compiling large solutions
Reduce file copy and read on solution build by improving heuristics on recognizing dlls that have not changed and/or introduce the concept of a class library build directory where all solution class library outputs are put, so dlls are not present at multiple places. Cache dlls in memory to reduce file IO. Etc.
This has already been part of the Visual Studio 11 features demoed so far. This should be marked by Microsoft as ACCEPTED so the people can get their votes back.
Justin Chase commented
I think you mean "responsive".