dotnet-best-practices

You can audit a target .NET solution to generate actionable best-practice guidance and a remediation plan covering architecture, dependency injection, resource management, and SOLID principles across namespaces like Core, Console, App, and Service.

Key .NET code quality standards include using primary constructor dependency injection, following SOLID principles, implementing proper async patterns, and ensuring robust resource management. These standards improve maintainability and consistency across libraries, services, and applications.

Yes, the .NET code quality guidance applies to both new development and refactoring scenarios. It provides structured patterns for libraries, services, and applications, ensuring consistent implementation of documentation, testing, configuration, and design patterns regardless of project maturity.

The best way to structure a C# project for SOLID principles is to enforce clear project structures, consistent namespaces, and interface segregation. Encouraging Command Handler and factory patterns alongside primary constructor DI ensures maintainable and well-segregated architecture.

Yes, the .NET best practices skill explicitly covers typed configuration and structured logging. It promotes robust validation and typed configuration to enhance testing and quality standards alongside enforcing XML documentation and SOLID-compliant code.

You need to audit your .NET solution for code quality when starting new development or refactoring existing projects. Auditing helps identify violations in async patterns, resource management, and dependency injection, generating a structured remediation plan to improve maintainability.