Exception handling at runtime seems a bit awful

As much as I love Rider in general, the handling of runtime exceptions when debugging seems awful.  Firstly, the exception display seems to involve looking at the watch window, then I have to scroll down a stack trace to find a point at which the error occurred in my own source code.

If I can find one, then I can click it and go and see the line where the error was thrown.

I've selected "Only my code" on the exceptions screen, but nothing seems to make it an acceptable experience.

Given that everything else works so nicely, is this simply something that has not yet caught up, or is there some aspect of the usability I'm missing?

1 comment

I have to agree with you Jason. I keep going back to visual studio everytime i get a problem with exceptions. Am i missing something?


Please sign in to leave a comment.