@vijayankit I've been using something similar in the past. I'm trying to simplify this. It's sort of too much ceremony. It seems the UseExceptionHandler is a nice fit. Also, it logs the exception before it invokes the lambda. Playing with this right now...

The "/Error" parameter passed to the UseExceptionHandler method specifies the URL of the error page that will be displayed if an unhandled exception occurs.

In the code, "app" is a variable that represents an instance of the WebApplication class that was created earlier. The "UseExceptionHandler" method is called on the app object to add the exception handler middleware to the web application's middleware pipeline.

Another way of handling exceptions globally in .NET - Use the inbuilt UseExceptionHandler() in Program.cs - It expects a route "/error" - Create a "/error" route in an ErrorsController - return Problem() result, Problem is compliant with RFC standards. #dotnet

@fonssonnemans @davidfowl Usually, I'd use the "UseExceptionHandler" instead of filters. I think it should work with minimal APIs. It seems it's not part of MVC as far I see (not sure about IFeatureCollection though) So, it will be something like this perhaps

ASP .NET Core’s IExceptionHandler + ProblemDetails = centralized, structured, user-friendly error handling. 1. Create a handler 2. Register (AddExceptionHandler()) 3. Enable (UseExceptionHandler()) Fail gracefully. Guide users. Log cleanly. #dotnet #csharp #backend #tech

@danpdc I would not call it "global" exceptions handling. Filters run within the #ASPNETCore action invocation pipeline. To handle exceptions "global" way you should #UseExceptionHandler as it goes first in middleware pipeline and really can handle the most of the exceptions

@peterritchie For backend I use the Global Error Handling (via app.UseExceptionHandler - don't mess with custom error handling middleware) as it's a built-in middleware which comes first so can handle all underlying exceptions. See #ASPNETCore #Middleware fundamentials https://t.co/91OTGzpeHB

https://t.co/zzzhJoAOFP Core: 未処理の例外に対してレスポンスのカスタマイズとか定型処理とかを実施するのは、UseExceptionHandler でエラー処理用のコントローラーにルーティングすれば OK みたい

Q: What is the purpose of UseExceptionHandler? A: It provides a global handler for unhandled exceptions and safe error responses.

With @aspnet core, you might have a few misbehaving endpoints. You can define a completely separate pipeline to handle exceptions with the UseExceptionHandler / IExceptionHandlerPathFeature that can access the original exception. #dotnet

What's your preferred way of global exception handling for APIs? - Action filters. - UseExceptionHandler lambda. - Your custom middleware. - Other #aspnetcore #dotnetcore

https://t.co/ZC8tqg6Kp5 #dotnet #webapi

Released a v4 beta of my GlobalExceptionHandler library. No major changes, just a few renames and breaking it from UseExceptionHandler() middleware.

@fiseni UseExceptionHandler + Endpoint With IExceptionHandlerPathFeature

https://t.co/ZTDhzlkatP Core API - Tratamento de erros com UseExceptionHandler - artigo de hoje no portal

@julioc Why would I use this over UseExceptionHandler?

Like the exception handling middleware collocates and does what I want. app.UseExceptionHandler(new ExceptionHandlerOptions { ExceptionHandler = async context => { // Do something with error }, ExceptionHandlingPath = "/Error" });

@jchannon More control over the response, it now ties into UseExceptionHandler api

@andrewlocknet working on porting on main app to #aspnetcore Working on exception handling and have three steps I want to do - narrow down error code - log to sentry - email devs Am I going down a dark path by having it all happen in UseExceptionHandler?