You are hereHome / Development / When Visual Studio becomes slow...
When Visual Studio becomes slow...
.. and I mean really slow, so slow
- it does nothing for about a minute each time you insert a new line in on of your code files
- each time you open a code file it's time for a coffee break
- setting a break point leaves you enough time to roll a cigarette
Then it's time to shut down, delete all the *.opt and *.ncb files from all your project directories and bring Visual Studio up again.
But beware: Deleting the *.opt files means loss of all information regarding your options! This is:
- The active configuration
- Working directory and programm arguments you entered in the project settings "debug" tab.
Actually this happens to me every once in a while. The reason are *.dsp files changing due to synchronization with CVS while the according projects are open in Visual Studio. Somehow, VS is not that good at handling the immediate reloading of project files, it seems.
Update: Len Holgate pointed out in a comment: It is enough to just delete all breakpoints. I tried it, and he's right. Neat!
Tags
Yup run into that myself. VS 05 is a bloody disaster. But by God they released it didn’t they! Quite an accomplishment I’d say, and hell it’s more than adequate for your typical “Hello World” program.
Sometimes you can get away with just deleting all of the breakpoints that have accumulated. It seems (at least with VC6) that sometimes code changes will cause breakpoint duplication and the slowdown is sometimes fixed by simply deleting them all.
Interesting. I will try it the next time. Thanks for the tip.
You really made my day with this breakpoint-deletion solution :-))))
I was about to go nuts because of it.
I guess you already know that when intellisense stops working you have to delete .ncb
No, I didn't know that about intellisense - since we replaced build in intellisense by a third party plugin called "Visual Assist" ;-). Visual Assist is highly recommendable at least for VS C++ 6.0, since VS's build in capabilities of intellisense are rather poor.
What do you mean by deleting the breakpoints? Isn't it just "removing" the breakpoints from the menu....or is it something else I am not aware of?
Cheers.
For anyone wondering how to delete the breakpoints in VC6:
Edit->Breakpoints->Remove All
or
Alt+F9->Remove All
Visual Studio 2005's breakpoints are horribly slow (compared to 2003), and it seems like it's mostly related to loading symbols, which becomes visibly slower each time you add a breakpoint.
Add a couple breakpoints, and the launch time (under the debugger) for our application is 3-4 times slower.
Hi,
Visual Studio was taking ~2 mins and sometimes over 30 mins (when I ended the task) to save files. I looked for .opt and .ncb and found none. However, the concept of problem files turned out to be right. I deleted the directorys containing the hundreds of files which made up the bulk of the solution and then pulled out only the ones we knew about from source control. Then, after more than a day of painfully trying all sorts of stuff to get it to work, finally it is saving (and therefore building) again!.
Hi,
I'm having this problem with Visual Basic 2005 but I can't fix it. I don't have any breakpoints and I've deleted all unnecessary files. I don't see any .opt or .ncb files. Every time I modify a line, VS2005 hangs for about a minute. It's impossible to do work.
Thanks.
Hi all, plz try to deactivate yours Anti-Virus...
THANK YOU !!!
Removing the breakpoints did the job, started my second day with the slow Studio
and this thing was killing me.