NetAgents.Analyzers 26.11.12.4219

✨ NetAgents

Consistent C# standards, enforced on every build.

Keep formatting, naming, and code quality consistent across your .NET projects. NetAgents automatically formats your source files and applies available code fixes when you build.

📦 Install

dotnet add package NetAgents.Analyzers

Requires the .NET 10 SDK or newer. Your projects can target older .NET versions.

Set PrivateAssets="all" on the package reference to keep the dependency private to your project. Shared rules apply automatically.

🛠️ Build and format

dotnet build

On each build, NetAgents:

1. Formats your source files and applies available code fixes automatically.
2. Checks the updated code against the shared rules.
3. Reports any remaining violations as build errors for you to resolve.

Builds can change your source files. Every rewritten file is named in the build log, including when the build then fails on a violation no fix can repair. A build that would leave behind a violation it introduced changes nothing at all and says so instead. Review those changes before committing. Some violations require a manual fix; IDE quick fixes and dotnet format are also available.

Unchanged builds reuse completed formatting after checking a content fingerprint of the sources, dependencies, tools, and configuration. Policy checks and compiler enforcement remain enabled. Profile a build with dotnet-trace; dotnet clean discards the record when a full run is wanted.

📏 Formatting rules

• Conditions: keep conditions on one line, with at most 128 characters. Extract longer expressions into separate variables. Ternary conditions follow this rule; their ? and : branches can span multiple lines.
• Arguments and parameters: keep lists on one line when their normalized contents fit within 128 characters, excluding the surrounding delimiters. Longer lists keep the first item beside the opening delimiter, put each later item on its own line one level deeper (one more for a list nested on the same line as another that continues), and close right after the last item; so does a list holding a lambda with several statements or a statement that holds others, such as if or try, one statement per line. This applies to calls and declarations, including constructors and records.
• Layout: use consistent spacing, blank lines between methods and around control flow and multiline declarations, braces based on body layout, every brace and statement of a statement block on its own line, an unbraced body on its own line below its header, and a final newline.
• Clarity: name literal and collection expression arguments, pass every other argument positionally, and remove unused imports.

🗂️ Member order

Members are sorted by kind, visibility, const/static/instance, readonly, then name. Nested classes follow methods. Overloads with matching sorting keys retain their relative order.

Sorting preserves initializer order and storage order in structs and types with explicit layout. Types containing preprocessor directives retain their member order.

✅ Code standards

C# written in Razor components and views (@code, @functions, and @{ } blocks, and event-handler lambdas) meets the type-safety, descriptive-name, reliability, concurrency, and tuple-result rules too. Formatting rules and fixes apply to .cs files.

Existing editor and project settings must agree with the shared rules. See the complete rule reference for details.

📦 NuGet package · 📖 Rule reference · ⚖️ MIT license