dotnet / dotnet/roslynator

Ruleset `<IncludeAll Action="Error" />` does not work with Roslynator.DotNet.Cli

Open
#982 2 comments 0 reactions 0 assignees View on GitHub
Area-CLI
Dominant language
C#
Stars
3.5k
Forks
294
Avg merge
2h 30m
Merged PRs (30d)
4

Description

**Product and Version Used**: Roslynator.DotNet.Cli
`
roslynator --version
0.4.0.0
`

**Steps to Reproduce**:
- Create a C# project in `VSCode`
- Add the following analyzer packages to `.csproj` (with the `dotnet add package` command):
- `Microsoft.CodeAnalysis` Version 4.3.1
- `Roslynator.Analyzers` Version 4.1.2
- `Roslynator.CodeAnalysis.Analyzers` Version 4.1.2
- `Roslynator.Formatting.Analyzers` Version 4.1.2
- Add some code that has some issues.
- Run `roslynator analyze`, output is:
![image](https://user-images.githubusercontent.com/17816598/200562184-79d6f6cf-1485-4e94-a5e6-2cf1b6191e38.png)
- Create a ruleset file manually, eg `\RoslynatorRuleset.xml`
- Reference the ruleset file in the `.csproj`: `RoslynatorRuleset.xml`
- Add the following content to the `RoslynatorRuleset.xml`:
```


```
- Run `roslynator analyze` again

**Actual Behavior**:
```
The same output is shown as in the screenshot
```

**Expected Behavior**:
```
All findings are marked as errors
```

I would like to thank you for your work with Roslynator.

What I would like to achieve is that my small Azure Function project written C# can be static checked in a CI build with the Roslynator.DotNet.Cli.
As far as I understood this setting in the ruleset file could be used to mark all findings as errors.
Setting `Action`s for specific rules in the ruleset file works, I can set rules to errors this way.

My another question would be about the settings for some rules, like the max line length check ([RCS0056](https://github.com/JosefPihrt/Roslynator/blob/main/docs/analyzers/RCS0056.md#rcs0056-a-line-is-too-long)).
Is it possible to somehow set the `roslynator_max_line_length` if I am using the Roslynator.DotNet.Cli in the CI? As far as I understood the .editorconfig files only work with Visual Studio but not with VSCode or the CLI.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.