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
The section "Places where errors may occur" shows all the places where an exception might be thrown, but the recommended resolution is wrapping the code with local try-catch statements. While we can add local try-catch to all the places, we might miss a few places and an unhandled exception might freeze the application.
Is there a way to implement a global exception handling, so we can catch any unhandled exception, like the ASP.NET custom errors? It would be useful to have a global exception handling so we can cover any unexpected exception while delivering a user-friendly page.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
ID: ce1440e7-febc-3fbc-09d7-7f47b740fd3b
Version Independent ID: 31071595-7c71-b6f7-3856-74f78c5c7cdf
The section "Places where errors may occur" shows all the places where an exception might be thrown, but the recommended resolution is wrapping the code with local try-catch statements. While we can add local try-catch to all the places, we might miss a few places and an unhandled exception might freeze the application.
Is there a way to implement a global exception handling, so we can catch any unhandled exception, like the ASP.NET custom errors? It would be useful to have a global exception handling so we can cover any unexpected exception while delivering a user-friendly page.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: