- My take on the Result class
- Functional C# Handling failures, input errors
- 10 Exception handling best practices in C#
- Exception handling in C# - throw or throw ex
- Problem Details - The right way to specify errors in Web API responses
- Handle Exceptions With ASP.NET Core ExceptionHandlerMiddleware
- Error handling: Exception or Result?
- Exceptions for flow control in C#
- C# code contracts vs input validation
- Fail Fast principle
- REST API response codes: 400 vs 500
- What is an exceptional situation in code?
- Functional C# Handling failures, input errors
- Prefer Custom Exceptions to Framework Exceptions
- CQRS and exception handling
- Using the ProblemDetails Class in ASP.NET Core Web API
- Handling Web API Exceptions with ProblemDetails middleware
- Creating a custom ErrorHandlerMiddleware function
- Clean code tips - Error handling
- Exception Handling in ASP.NET Web API - A Guided Tour
- Problem Details for Better REST HTTP API Errors
- Global Exception Handling in ASP.NET Core – Ultimate Guide
- ASP.NET Core 3.1 - Global Error Handler Tutorial
- Global Error Handling in ASP.NET Core Web API
- Mapping exceptions to HTTP responses with .NET Core
- Setting up an Exception Mapper in .NET Core 2.0
- Using Middleware to trap Exceptions in Asp.Net Core
- Centralized exception handling and request validation in ASP.NET Core
- Error Handling and ExceptionFilter Dependency Injection for ASP.NET Core APIs
- Global Exception Handling in ASP.NET Core WEB API
- Scaffold Your Clean DDD Web Application - Part 4: Global Exception Handling in ASP.NET Core and Angular
- An opinionated way to consistent Error Handling in ASP.NET Core
- EXCEPTION HANDLING MIDDLEWARE IN .NET CORE WEB API
- Cost of exceptions
- The True Cost of .NET Exceptions -- Solution
- Design Guidelines Update: Exception Throwing
- Why Exceptions should be Exceptional
- Exception Throwing
- Using Standard Exception Types
- Exceptions and Performance
- Improving .NET Application Performance Part 10: Exception Management
- Bad Data, Try/Catch, and Slow Performance
- Exceptions and Performance
- CARE your Web APIs with Consistent and Structured Error Responses
- HTTP API Problem Details in ASP.NET Core
- Problem Details: A standard way of specifying errors in HTTP API responses
- Handle errors in ASP.NET Core
- ASP.NET Core 8: Improved exception handling with IExceptionHandler
- STOP throwing Exceptions! Start being Explicit
- BEYOND Status Codes! Better REST HTTP API Error Responses
- The hidden cost of Exceptions in .NET
- Don't throw exceptions in C#. Do this instead
- The Exception Mistake You Must Never Make in C#
- proudmonkey/AutoWrapper
- khellang/Middleware.ProblemDetails - Various ASP.NET Core middleware
- ardalis/GuardClauses - A simple package with guard clause extensions.
- JosephWoodward/GlobalExceptionHandlerDotNet - Exception handling as a convention in the ASP.NET Core request pipeline.
- safakgur/guard - A high-performance, extensible argument validation library.
- FluentValidation/FluentValidation - A popular .NET validation library for building strongly-typed validation rules.
- mcintyre321/OneOf - Easy to use F#-like
discriminatedunions for C# with exhaustive compile time matching - ardalis/Result - A result abstraction that can be mapped to HTTP response codes if needed.
- altmann/FluentResults
- ikyriak/ConsistentApiResponseErrors - A .NET Core middleware that centralizes the handling of input-validation errors, application exceptions and unhandled exceptions.