Continued in Visual Studio debugger after exception

Question

When I debug a C # program and I get an excluded thrown (either thrown by code or created by the framework), the IDE stops and returns me to the corresponding line in my code.

Now everything is all right.

Then press "F5" to continue. From now on, he stitches, as if I'm in an endless loop. The IDE always returns me to the exception string. I have to Shift + F5 (stop debugging / terminating the program) to exit it.

I talked to some of the staff here, and they told me that this happens to them as well.

What's happening?

Answer 1

This is because the exception is not handled, and Visual Studio cannot move along this line without processing it in any way. Simply put, this is by design.

One thing you can do is drag the execution point (yellow line / arrow) to the previous point in the code and change the values ​​in memory (using the Visual Studio viewport) so that they don't throw an exception. Then go through code ¹ again.

It is best to stop execution and fix the problem causing the exception, or handle the exception correctly if the throw is not needed.

_{¹ This can have unintended consequences, as you essentially re-execute some code (without rewinding the execution).}

Answer 2

You probably have the option “ Unbind column on unhandled exceptions ” in Visual Studio. When this option is in Visual Studio, it will expand until the exception itself, so pressing F5 will continue to work in the same exception.

If you disable the Visual Studio option, it will be broken into an exception, but pressing F5 will go through this line.

This option is located in the menu Tools → Options → Debugging → General.

Answer 3

When the IDE breaks into an offensive line of code, it stops just before the line that throws the exception is executed. If you continue, it will execute this line again and get an exception again.

If you want to bypass the error to find out what would have happened if the error had not occurred, you can drag the yellow highlighted line (the line that will be executed further) to the next line of code after violation one. Of course, depending on what could not be executed in the line of violation, your program may now be in a state that causes other errors, in which case you have not helped yourself very much and probably should fix your code so that the exception either not executed 't happening or being handled properly.

Answer 4

Once you get the exception, Visual Studio (or any other IDE you could use) will not let you go further if the exception is not handled in your code.

This is design behavior.

Answer 5

Continuous exclusion will reduce your application. Instead, VS will simply take you away from the uncaught exception, you will have to stop or use the feedback from your application.