#resultpattern#errorhandling#exceptions
169K subscribers • 11 videos on Hallway
Intermediate. Assumes working knowledge.
79K views2 years ago2 recommendations
Software designProgramming languagesC# and .NETDesign patternsFunctional programming
Milan Jovanović compares throwing exceptions with returning a Result object for domain validation, showing how to implement the Result pattern in C#.
Get the source code for this video for FREE → the-dotnet-weekly.ck.page/result-pattern ☄️ Master the Modular Monolith Architecture: bit.ly/3SXlzSt 📌 Accelerate your Clean Architecture skills: bit.ly/3PupkOJ 🚀 Support me on Patreon to access the source code: patreon.com/milanjovanovic I will show you two approaches for Domain validation with .NET. The first approach will be based on throwing exceptions. The second approach will be based on returning a result object. I'll show you how to extend the Result pattern with errors and clean up your design. It's more performant and expressive than throwing exceptions. Which validation approach would you choose? I prefer expressing errors using the Result pattern. Join my weekly .NET newsletter: milanjovanovic.tech Read my Blog here: milanjovanovic.tech/blog Chapters Why I don't prefer throwing exceptions Returning error messages instead of throwing exceptions Adding an Error type express errors in the domain Documenting domain errors for a better design Using a Result object to represent success or failureWhat people say. Recommended for learning how to implement the Result pattern to handle errors cleanly without throwing exceptions.
u/INN_Ginein r/dotnet • Recommends
On “Is there a modern best practice for return types?”
u/blazor_tazorin r/dotnet • Recommends
On “How can I return a 404 error from a service in ASP.NET Core?”