csharp-style-guide

You can enforce C# coding standards by applying automated style-guide checks to touched .cs, .csproj, and .razor files during pull requests. This validates naming conventions, nullability annotations, and API design to ensure consistent coding practices.

The best way to validate async patterns and nullability in .NET code reviews is to run an automated style evaluation that flags violations and suggests refactors for unsafe async usage and missing nullability annotations across C# artifacts.

Yes, you need dotnet-format, dotnet-build, and dotnet test to run automated C# style checks in CI. These dependencies are required to validate naming, nullability, async usage, and API design against enforced quality guidelines.

Yes, you can use a C# style guide to check .csproj, .props, and .targets files. The evaluation applies to these project file formats alongside .cs, .sln, and .razor files to ensure consistent coding practices across all .NET artifacts.

Your C# code review fails on API design and boundary testability because the style evaluation actively guides code structure and error handling, ensuring boundary and testability considerations are respected before changes can be approved.

You should not use an automated C# style guide when modifying files outside the supported .cs, .csproj, .sln, .props, .targets, and .razor formats, as the evaluation specifically targets these .NET artifacts to catch design issues early.