I have a very serious problem with Visual Studio 2008. Occasionally when I right-click (for go to definition, set next statement etc) when I'm debugging, Visual Studio will just dead-lock and go into not responding mode.
Has anyone had the same problem? Does anyone know how to solve it?
Edit: I'm using SP1 with a couple of hot-fixes.
no, but it sounds like a bug. Report it to MS and they'll give you instructions how to get a debug setup going to send them information to debug it.
Mark, have you applied the SP1?
I haven't had your exact issue, but I did have problems with it locking up for 15 seconds in debug mode (or when coming out of debug mode). I found a blog post somewhere that suggested some possible fixes.
One of them was to go into IE 7 and open up Tools->Internet Options->Advanced Tab->Security section and uncheck the 'Check for publisher's certificate revocation' and 'check for server certificate revocation' (or at least the first one). Once I did that, my lock-up woes were over.
Granted, my dev box isn't on the internet, so I didn't care much about most of those settings anyhow in IE. Don't know if that is any help to you, but it certainly fixed my issues with VS 2008.
All the best!
I wrote a piece of code the other day, a very crazy template, and the latest VisualStudio would just hang if I placed my mouse over the templated code. It was surreal :)
Anyways you might have an issue like that and you might want to delete your intellisense database and try again.
Ah another big show stopper could be "ActiveDirectory". If this happens at your work and they use "ActiveDirectory" this can happen. Someone here claimed it was a bug with Google Toolbar, but I don't have solid evidence that Google is responsible or not.
When debugging multi-threaded apps, sometimes I get a hang when breakpoint is hit. And sometimes VS would hang (hourglass) when I tried to look at a variable by right-clicking on the variable within the code.
I googled and found a hint that explained, that when VS breaks, it evaluates all the variables in the locals and watch panes, in order to display them. But in threaded apps, this can cause deadlocks if the code takes locks when evaluating values, for example in property getters.
By closing the locals pane before I break, I avoided the hangs.
I'm not explaining this very well. I tried googling again to find the original hint, but did not succeed.
It may have been this: Why does Visual Studio stall while debugging?.
I find Visual Studio (VC9) locks up regularly when debugging multithread apps. I usually have to reboot to get the system back.
For me I found that VS was trying to open an IP that had expired for when I did some previous remote debugging. Check your Debugging setup under Tools-->Options-->Debugging--->Symbols Make sure you don't have a bad path there.
This issue no longer occurs for me since I've moved to Windows7. If you're unfortunate to be stuck with Windows Vista still, I did discover that it only hung on right-click when waiting for the intellisense database to be built (see the bottom left corner for it's progress). The only "fix" I had was to wait for intellisense to stop building, then do a right-click.