Debugger: Ignore exceptions thrown in data portal methods caught on client

[swegele]

When debugging our tests in Visual Studio 2019 on a project with our CSLA business objects:

Obviously some of our tests purposefully trigger code that throws exceptions on server side of the data portal (e.g. in DataPortal.Fetch etc.). These exceptions ARE CAUGHT in try/catch on client side of data portal or in the tests themselves in Assert statements. But the visual studio debugger stops at the close of the DataPortal.Fetch method prompting with an Uncaught message. This forces me to have to repeatedly hit "F5/Play" as I'm walking through the various tests. This gets really annoying. Any tips or tricks from you gurus to get visual studio to stop thinking those are uncaught?

Thanks

[swegele]

Wow it was so simple. Uncheck the box "Break when this exception type is user-unhandled"
Now I don't get pestered with VS breaking on these over and over while debugging tests.