ASP.NET Core 8 uses IExceptionHandler for global exception handling

Little scum · Posted on 6/3/2024 9:21:04 AM

Requirements: In order to maintain a consistent request response data format with the front-end, the back-end needs to format the global exception, and then the front-end receives the exception information and provides friendly prompts.

Before IExceptionHandler comes out, we need to write an exception catching middleware, and the middleware code uses try-catch to catch and respond.

ASP.NET Core 8 introduces new ones for managing exceptionsIExceptionHandlerAbstract. The built-in exception handler middleware uses the IExceptionHandler implementation to handle exceptions.

The interface has only one TryHandleAsync method.

TryHandleAsync attempts to handle the specified exception in the ASP.NET Core pipeline. If the exception can be handled, it should return true. If the exception cannot be handled, false should be returned. This allows you to implement custom exception handling logic for different scenarios.

When our controller throws an exception, the code is as follows:

Login is visible.

If you do not handle exceptions, the default response in the production environment is as follows:

Create a new GlobalExceptionHandler exception handler with the following code:

Login is visible.

Then program the exception handler is registered, and the code is as follows:

Login is visible.

Tried to access the exception controller and the response was as follows:

Reference:

The hyperlink login is visible.
The hyperlink login is visible.
The hyperlink login is visible.

[ASP.NET] ASP.NET Core 8 uses IExceptionHandler for global exception handling

Related Posts

Sections viewed