[BUG] Breakpoints section has "All Exceptions" breakpoint missing and there's no way to add it manually · Issue #1715 · microsoft/vscode-dotnettools · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've struggled with the problem that "All Exceptions" breakpoint have just disappeared from my breakpoints section in Run and Debug tab.
I am using VS Code with C# dev kit and MAUI extensions in order to build and debug iOS and Android apps. "All Exceptions" breakpoint is crucial for development, actually it would be great to manually add exception breakpoints with some conditions and specific exception types, as we can in Visual Studio for Mac which is unforgivably abandoned by Microsoft.
Previously at least there were default "All Exceptions" and "Unhandled by user exceptions" breakpoints. But now, due to some unknown reason, these are gone. And now I can only manually add breakpoints, but there's no option for creating an Exception breakpoint. I've searched through the web and issues here for some possible solution, but unfortunately didn't find anything suitable, thus, please, help with finding at least some workaround or, maybe, possible solution.
P.S. Also, in the latest MAUI extensions preview you have removed the ability to disable the new debugger for .NET8+, which is very bad, since the new debugger doesn't work properly with iOS projects, at all.
Steps To Reproduce
Run any .NET8.0 Android or iOS project
Go to breakpoints section in run and debug
Expected Behavior
There's an ability to turn on All Exceptions breakpoint (or even create some custom exception breakpoint).
Strangely enough, it is not the case for all of the projects. Some have "All Exceptions" and "User-Unhandled Excpeions" option, and some doesn't. Maybe someone could point out what can be the reason that it works that way
Hi @Saratsin.
The breakpoints panel shows after you debug the project once. You can verify the same behavior with a new .NET console app.
Since we migrated to use the new debugger by default (if you have at least dotnet 8.0.101), you should see this panel for MAUI and iOS/Android .NET apps.
Can you confirm if you see this with latest C#, C# DevKit and .NET MAUI versions? You should be able to see the panel and the "All Exceptions" and "User-Unhandled Exceptions" options normally once you enter in a debug session the first time.
We've tried several times in different environments and it always worked.
Thanks
Uh oh!
There was an error while loading. Please reload this page.
Describe the Issue
I've struggled with the problem that "All Exceptions" breakpoint have just disappeared from my breakpoints section in Run and Debug tab.
I am using VS Code with C# dev kit and MAUI extensions in order to build and debug iOS and Android apps. "All Exceptions" breakpoint is crucial for development, actually it would be great to manually add exception breakpoints with some conditions and specific exception types, as we can in Visual Studio for Mac which is unforgivably abandoned by Microsoft.
Previously at least there were default "All Exceptions" and "Unhandled by user exceptions" breakpoints. But now, due to some unknown reason, these are gone. And now I can only manually add breakpoints, but there's no option for creating an Exception breakpoint. I've searched through the web and issues here for some possible solution, but unfortunately didn't find anything suitable, thus, please, help with finding at least some workaround or, maybe, possible solution.
P.S. Also, in the latest MAUI extensions preview you have removed the ability to disable the new debugger for .NET8+, which is very bad, since the new debugger doesn't work properly with iOS projects, at all.
Steps To Reproduce
Expected Behavior
There's an ability to turn on All Exceptions breakpoint (or even create some custom exception breakpoint).
Environment Information
macOS Sonoma
| VS Bug 2381924
The text was updated successfully, but these errors were encountered: