Rider exception handling
I got the following exception setting in Rider
If I run my application initally and setup a exception, the runtime stops at the exception right away:
That's fine. I would expect that it behaves the same way with the settings above (at least in my code).
Now when I execute some other static user code, Rider will not stop at at any exception raised in a similar way. 
Ofcourse I can still figure it out by subscribing to AppDomain.CurrentDomain.UnhandledException stacktrace is unwound. But I want the debugger to stop at the very exact line of code where it got raised like in the screenshot above.
Since that static user code is in a large utilities assembly of our company I cannot narrow down the code which causes the issue easily. Also that assembly got more dependencies.
So I would like to approach this in a more general way: Is there any code / project configuration with can influence the way Rider handles the exceptions?
Please sign in to leave a comment.
In the latest version of Rider, if you select Mute and Resume some exception breakpoint, the exceptions will be added into the “suspend list” of breakpoint configurations.
In this situation, the same type of exception will not be triggered in the further debug sessions. You can untick the auto added exception types in the list. See the related debugger documentation here.
Thanks for your response.
As you can see in my screenshot I don't have any specific exception type configuration settings, so all the exceptions should be treated the same right?
Also, that would not explain the different IDE behavior depending on the code which was executed.
May I know if you can provide me a sample code snippet of the situation?
The case I shared is a common question that developers may misunderstand the “Mute and resume” button usage - it will mute the dedicated exception types in all following debugging sessions. I guess you were in the same situation.
But if you just resume the debuggee, the debugger definitely should suspend on the similar unhandled exceptions again, unless the exception types are muted.
I see.
Unfortunately, I do not have any muted exception in my exception settings.
The static code which is invoked right before the exception handling is not working anymore is in a utility library from our company, so unfortuntately I cannot share it with you. Also it's a quite large code base, so it's hard for me to track down the source of the issue.
That's why I wanted to ask in a more general way, if there is something “code can do to rider” to produce the behavior.
If the exception types were note been muted all the time (even in the debug session, you can check the breakpoint status window anytime), it could be a debugger issue.
Besides try with the latest Rider version, you can create a support request in Help | Contact Support. We will guide you collect IDE logs and investigate futher on the issue.
I tried that but unfortunately, the support is only available for paying customers right?
You can create a new issue with detailed information about reproducing the problem on YouTrack. You can also attach your logs on the ticket for further investigation.