dotnet-code-validation

To enforce C# code quality and DDD patterns, you validate code against project `.editorconfig` rules, ensuring correct separation across Domain, Application, Infrastructure, and API layers. This guarantees adherence to naming conventions and architectural standards.

Validating CQRS separation and FluentValidation usage involves checking that commands and queries remain distinct and that validation logic is correctly applied. This ensures your C# code maintains clean architectural boundaries and robust input validation.

To ensure C# domain entities follow immutability rules, you enforce the use of private setters and validate that methods use domain-specific terminology. This maintains strict Domain-Driven Design principles and consistent entity behavior.

Yes, you can use this to check adherence to `.editorconfig` formatting and specific C# style preferences. It validates indentation, modifiers, and formatting rules to guarantee consistent code style across your software project.

A limitation of automated coding standards validation is that it primarily checks structural and stylistic compliance, such as `.editorconfig` rules and DDD patterns. It cannot fully evaluate broader architectural context or subjective domain logic design decisions.