المدة الزمنية 29:54

Exception Handling for Core Web API

بواسطة Julio Casal

7 063 مشاهدة

201

تم نشره في 2023/03/28

💻Join me on Patreon to get the source code: https://www.patreon.com/juliocasal 🔥My Free .NET Backend Developer Roadmap: https://juliocasal.com/roadmap 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 📰Join my weekly .NET newsletter: https://juliocasal.com/newsletter Patreon: https://www.patreon.com/juliocasal LinkedIn: https://www.linkedin.com/in/juliocasal Twitter: https://twitter.com/julioc #csharp #dotnet #aspnetcore

عرض المزيد

تعليقات - 23

@

@onlythestrongsurviveقبل 3 أشهر I learned a lot with this tutorial. Thank you 1
@

@broadshareقبل 5 أشهر Thank sir, have learned a lot from your tutorials. 1
@

@pedroferreira9234العام الماضي Hey Julio, thank you for the video!
Would be cool if you extend this video for people that program to exceptions.
@

@Marfigقبل 6 أشهر 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, id="hidden1" class="buttons"> my endpoints should instead return their own problem details object and not go through this middleware. Is that correct? ....وسعت 1
@

@veeramuthurقبل 7 أشهر 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 id="hidden2" class="buttons"> 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 ....وسعت 1
@

@bycarstenقبل 7 أشهر Nice approach, but can i use Try and Catch in my code to override this?