VS.NET, Debugging...
There was a recent MSDN Chat regarding the debugger which I attended (to get to the bottom of this issue). Here's part of the log:
------------------------------------------------------------
Q: Debugging is really slow and pegs cpu withen 20-30 projects are present in a solution
A: This is likely a soultion/project system perf issue, we are goign to follow up with the project system team later to see if they are working on this or have a workaround
Host: habibh (Microsoft): Q: Rob_Chartier_[MVP] - Are the performance issues only around stepping or does it also include startup time? Also, are these all VB.NET or C# projects?
Q: Rob_Chartier_[MVP] : startup time is never an issue
A: I suspect that the issue is around property evaluation. The next time that you debug, can you try closing all your data windows (e.g. Watch, Autos, etc.)? We have done a fair amount of work to improve the perf. for stepping.
------------------------------------------------------------
The important thing here is to ensure that all your data windows (e.g. Watch, Autos, etc.) are all closed BEFORE you enter into debug mode. If you close all of these AFTER you will still see the performance issue. I was bored and was playing around with the IDE and closed all the windows at design time in order to find this out. It appears to have solved the issue, for now. Now if I can only find out why it is locking a project/assembly in my middle tier causing me to restart VS.NET all the time when I need to rebuild that one specific project. *sigh*
Lastly, notice this:
Q: (Rob_Chartier_[MVP]) Edit and Continue for both C# and VB.NET. Can we expect it?
A: Unfortunately, Rob, you cannot expect Edit and Continue for C#. Things like refactoring and other IDE enhancements took precedence. Sorry.