Operating system: Windows 11 Enterprise 23H2 Visual Studio version: 2022 Patch 17.14.21 SonarQube for Visual Studio plugin version: 9.0.0.15771 Programming language you’re coding in: C# Is connected mode used: yes SonarQube Cloud, SonarQube Server, or SonarQube Community Build? (if one of the latt…

Hi. Are you sure that it’s the case? The first link I’ve sent you had a bug: we didn’t link the configuration file to the project, so it shouldn’t have worked at all. The second link is the one that should fix that and disable the cleanup for our rules. The cleanup of no longer necessary pragmas w…

Hi, sorry I messed something up. I saw my visual studio auto updated the first version I installed to the latest one 9.8.0.16314 and while trying the second link and installing, something seems to went wrong and it looks like it went back to an older version. however the new version https://github…

Does the TreatWarningsAsErrors functionality work for you? It was also added in the same release

I see sonar issues in the report view, but not as an error. Same for the “Error List” View. I see the issues there as “Message” for example for the S2094. At least as error or warning would be great, because we have the policy to have no warnings and errors, but mostly not look at the “Message” list…

The mapping depends on your quality profile - sonarlint-visualstudio/src/IssueViz/Helpers/IAnalysisSeverityToVsSeverityConverter.cs at f9145509ead7abff8dd59cfafd09c64aa71f140d · SonarSource/sonarlint-visualstudio · GitHub . Without the TreatWarningsAsErrors property you should see messages and warn…

Hi, I have [image] and this is the result in Visual Studio 2022 [image] The issue is not as a warning or error in the list for example. Greetings

but I saw the issue S1541 for example is shown in the error list

What is the Sonar severity of S2094 in the Report view? If it’s Info or Low - that is expected. TreatWarningsAsErrors should only affect issues with Medium, High and Blocker severities

We can test it with a simple issue ‘“async” and “await” should not be used as identifiers’ csharpsquid:S2306 Can you add this to your code: int await = 42; // Noncompliant, but compiles int async = 42; // Noncompliant, but compiles

async and await issue is shown as error yes. Maybe the S2094 severity is to low. Where can I find the severity in the report view? [image] And could it be possible to customize that, that also “Info” and “Low” severities is treated as errors? We have nearly all Sonarqube rules active with only a …

Sonarqube for IDE [Visual Studio] issues/questions

SonarQube for IDE Visual Studio

georgii.borovinskikh (Georgii Borovinskikh) March 5, 2026, 8:07am 33

Hi. JFYI There’s an issue with the implementation: SonarQube Reporting Multiple Global Analyzer Warning Message in Brand New Project

Not sure why this is happening, but I might need to disable the disabling of cleanup for our issues

Topic		Replies	Views
VS Project property TreatWarningsAsErrors will show Sonarqube issues with red squiggles Visual Studio	8	171	June 27, 2025
SonarQube for IDE 9.x ignores NoWarn, SonarQube server & IDE 8.x respect it Visual Studio	12	68	January 29, 2026
SonarQube for IDE: Visual Studio 9.8 - Enhanced Control & Reporting Releases visualstudio	0	37	March 9, 2026
Missing Sonar rules in "Suppress or Configure Issues" in raised Warnings Visual Studio	3	90	April 13, 2026
Issue reporting stopped since version 9.0.0 in VS Visual Studio bump , free	38	440	January 2, 2026

Sonarqube for IDE [Visual Studio] issues/questions

Related topics