Adding .editorconfig breaks TreatWarningsAsErrors

[JimBobSquarePants]

Describe the bug

Adding the .editorconfig file from repo main breaks TreatWarningsAsErrors

To Reproduce

1. Download the attached project ErrorsTest.zip
2. Set build configuration to Release and build.
3. StyleCop warnings are not treated as errors and do not cause the build to fail.
4. Remove .editorconfig file and rebuild. Build will fail.

Expected behaviour

When the build configuration is set to release the build should fail.

Rules

Provide links to any rules in question.

[JimBobSquarePants]

Removing this line appears to fix the issue.

EditorConfig/.editorconfig

Lines 71 to 74 in 7b1927e

	[*.{cs,csx,cake,vb,vbx}]
	# Default Severity for all .NET Code Style rules below
	dotnet_analyzer_diagnostic.severity = warning

Replacing with specific defaults is advised otherwise all warnings become errors.
e.g.

dotnet_analyzer_diagnostic.category-style.severity = warning

Related issue
dotnet/roslyn#43051

[RehanSaeed]

Thanks @JimBobSquarePants! I was following that Roslyn thread and thought this was fixed since they closed the issue but perhaps not.

Which version of VS are you using? dotnet_analyzer_diagnostic.severity should have been working since VS 16.9 onwards but I wonder if there have been bug fixes in 16.10 or 16.11 preview.

[JimBobSquarePants]

No worries 😄
I'm using VS 16.10.

[RehanSaeed]

Raised new issue dotnet/roslyn#55541.

[JimBobSquarePants]

Looks like there was a fix for this issue. Perhaps it can be closed now?

dotnet/roslyn#58460

[RehanSaeed]

Looks like the fix was rolled out in 17.2. Closing. Thanks for reporting.