Exception Handling for ASP.NET Core Web API | .NET 7

Learn the right way to handle exceptions in your ASP.NET Core Web APIs to ensure you don't miss any critical errors and to collect essential info for troubleshooting.

Topics covered:
05:17 The try...catch approach
12:09 The middleware delegate approach
16:25 The middleware class approach
23:09 The UseExceptionHandler approach

#csharp #dotnet #aspnetcore

[broadshare]

Thank sir, have learned a lot from your tutorials.

[onlythestrongsurvive]

I learned a lot with this tutorial. Thank you

[pedroferreira]

Hey Julio, thank you for the video!
Would be cool if you extend this video for people that program to exceptions.

[Marfig]

Thank you. Very useful explanation! I gather this is only meant to be used with unhandled exceptions. For all those cases where I want to throw a 4XX error, my endpoints should instead return their own problem details object and not go through this middleware. Is that correct?

[veeramuthur]

my dotnet core application is communicating to microservice. from microservice i am getting 400 error, but my dotnet core app is coverting to 400 to 500 status code storing in azure log as 500 (server is not found ) how its possible. i want to store same 400 into my azure logs. can you please suggest better way? thanks advance

[bycarsten]

Nice approach, but can i use Try and Catch in my code to override this?