views:

602

answers:

2

F12 is a wonder for tracking down UI blocking operations, but I can't figure out how to make it work with VS 2008 and managed code.

Help! Or not...

Edit: turns out it doesn't work in VS 2005 either on Vista x64, so I guess that either widens or narrows it down, depending on your perspective :(

MSN

A: 
Milan Gardian
In your question you're mentioning you're already debugging your application - in that case you only need to run the "Break all" command (because the process being debugged is already attached). Fastest solution IMHO would be to focus Visual Studio and hit the "Break all" keyboard shortcut.
Milan Gardian
It's not as fast as hitting F12. Or rather, hitting F12 takes **much less time** than switching apps and hitting Break All. Trust me, it's awesome when it works.MSN
MSN
A: 
Milan Gardian
So I take it this solution is not helpful either?
Milan Gardian