- Design validations in the domain model layer
- REST API Data Validation
- Domain Model Validation
- Validation in a DDD world
- Domain Command Patterns - Validation
- Validation in Domain-Driven Design (DDD)
- Validation and DDD
- C# code contracts vs input validation
- The fallacy of the always-valid entity
- When to validate commands in CQRS?
- Exceptions for flow control in C#
- Fail Fast principle
- REST API response codes: 400 vs 500
- Functional C# Handling failures, input errors
- Prefer Custom Exceptions to Framework Exceptions
- CQRS and exception handling
- Error handling: Exception or Result?
- What is an exceptional situation in code?
- Validation and DDD
- Cool validation with FluentValidation
- Validation inside or outside entities?
- Custom Validation in ASP.NET Web API with FluentValidation
- Exception Handling in ASP.NET Web API - A Guided Tour
- Scaffold Your Clean DDD Web Application - Part 4: Global Exception Handling in ASP.NET Core and Angular
- Advanced error handling techniques
- Combining ASP.NET Core validation attributes with Value Objects
- Always-Valid Domain Model
-
GuardClauses - A simple package with guard clause extensions.
-
danielwertheim/Ensure.That - Guard clause project for .NET
-
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.