Currently, if running a composite launch profile with for example .Net and Chrome configurations simultaneously, there is only one Exception Breakpoint profile for both. This is an issue because JS in the browser and .Net have very different ways of treating errors.

In JS, especially in the browser, it's very common to purposefully trigger errors for the purposes of determining when polyfills are needed. These errors are meaningless to the end-developer most of the time and thus the developer will want to ignore the thousands of caught errors polyfills trigger. (Of course, the polyfill developer may think they are important and so they may need to break on caught errors.)

On the other hand, in .Net it's very likely that your very meaningful Exception has been caught by .Net for the purposes of finishing the MVC middleware pipeline and returning meaningful information to the developer via the Developer Exception middleware. Thus, when debugging Exceptions in .Net, it is usually important to debug Caught exceptions.

Unfortunately, when checking Caught exceptions for .Net, one must Continue through thousands of polyfill errors in Chrome, or use a different browser just to trigger a request where Caught exceptions are being debugged. This may also be an issue if you are using JS + .Net microservices in tandem.

I think #126608 is related, but it doesn't include the fact that the breakpoint profiles are actually the same. I believe the PHP debugger actually uses different terminology (Errors, Exceptions, Everything) to refer to Break on Exception and thus they may actually not conflict the way Chrome, NodeJS, and .Net exceptions do.