Agent RulesAgent Rules
VB

dotnet-format + Roslyn VB

dotnet-format and Roslyn analyzers for VB.NET code quality and style enforcement

Visual Basic .NET
Linter / Formatter
Default
Use in BuilderAll Visual Basic .NET Options

Details

Language / Topic
vbnetVisual Basic .NET
Category
Linter / Formatter

Rules

balanced
- Run `dotnet format` with the `--include` flag targeting `*.vb` files to auto-fix formatting violations defined in `.editorconfig`.
- Configure `.editorconfig` with `[*.vb]` section for VB-specific settings: `indent_size = 4`, `end_of_line = crlf`, and `vb_new_line_before_query_clauses = true`.
- Enable Roslyn analyzers in `.vbproj`: `<EnforceCodeStyleInBuild>true</EnforceCodeStyleInBuild>` to fail the build on style violations.
- Use `dotnet format --verify-no-changes` in CI pipelines to reject pull requests that contain unformatted VB.NET code.
- Configure Roslyn diagnostic severity in `.editorconfig`: `dotnet_diagnostic.IDE0059.severity = warning` for unused value assignments.
- Use `Roslynator` NuGet package for additional refactoring and analysis rules beyond the built-in Roslyn set.
- Add `.editorconfig` to the repository root and commit it — Visual Studio reads it automatically and applies formatting on save.