Stop current operation in Visual Studio

Question

When using Visual Studio, I often encounter situations where the IDE hangs during some operation. For example, this often happens when I move the next operator pointer (yellow arrow) during a debugging session, when I inadvertently press F1, go to some low-level function that has multiple instances in binary, etc.

In these situations, the Visual Studio notification widget appears in the tray with the following text:

Microsoft Visual Studio is busy

Microsoft Visual Studio is waiting for the completion of the internal operation. If you experience this delay regularly during normal use, report this problem to Microsoft.

Often the delay is so great that it is faster to kill the Visual Studio process, restart it, restart the debugging session (or something else I'm doing) and avoid the operation that caused such a delay. However, this still takes too much time. I would like to have a way to stop / cancel an operation that takes so long. For example, in Total Commander, this is possible by pressing Esc during such an operation.

Is this possible with Visual Studio? Any plugins that allow this to be done? Any other way around the problem?

PS Sorry for the detailed description, but I wanted to explain the actual problem (not to ask if some solution is possible) so that people can come up with ways to solve the problem.

PPS This problem is in 2008 and in 2010.

Answer 1

If you are debugging, try pressing SHIFT-F5. This should stop the debugger, although probably not immediately, faster than you described. The program will process the keyboard much faster than trying to click the menu with the mouse.

If you are building, try pressing CTRL-Break. Again, this may take a few seconds, but this usually happens.

I had a problem that you talked about a few years ago, but I don’t remember what I ultimately did to fix it.

Answer 2

There can be many different reasons for this problem, but for me, the slowdown was apparently an attempt to download characters from character servers. I disabled the location of the symbol files (.pdb) in the Debugging \ Symbols options and the problem completely disappeared.

Answer 3

run iisreset can solve your problem start → iisreset.exe