SonarQube for IDE 9.x ignores NoWarn, SonarQube server & IDE 8.x respect it

SonarQube for IDE Visual Studio
1

Please provide

  • Operating system: Windows 11
  • Visual Studio version: 2026 18.2.0 (also seen in 18.1.1)
  • SonarQube for Visual Studio plugin version: 9.3.0.15979 - trying to upgrade to latest, having difficulty getting it to install, but also don’t see anything obviously relevant in the release notes of later versions.
  • Programming language you’re coding in: C#
  • Is connected mode used: SonarQube Community Build 26.1

And a thorough description of the problem / question:

We use NoWarn in our .csproj file to disable S3216 (ConfigureAwait(false)) for specific projects where it should not be used (i.e. ASP.NET projects).

This works fine in VS2022, SonarQube for IDE 8.14.0.12562, connected to the same SonarQube server. The rule is suppressed in these projects when the code is analyzed by SonarQube server (which is probably still using VS2022). But I’m seeing S3216 warnings in the IDE with 2026/9.x for these projects.

2

Hi,

Could you provide a verbose log from IDE startup through to the problem?

 
Thx,
Ann

3

verboselog.txt (179.1 KB)

5

Hi,

Thanks for the log! I’ve flagged this for the experts.

 
Ann

7

Hi @HamsterExAstris

We did a change to how we run analysis in 9.0, but it is a bit unexpected that this doesn’t work. I will look into fixing it.

But for this specific case, it could also be possible for our analyzer team to make the permanent exception to the rule based on the ASP NET context, I will contact them and see if it makes sense

8

BTW, could you also explain what problems are you facing with the extension update?

9

When I trigger the update inside Visual Studio, it will download the update, but it doesn’t trigger the install when Visual Studio is closed. If I update another extension at the same time, that does install, so it’s specific to the SonarQube extension.

Manually downloading and installing the VSIX worked this time.

10

Hi. I tried to reproduce the problem, but NoWarn seems to work for me. I tried it with a different rule, but it shouldn’t matter

<PropertyGroup>
  <TreatWarningsAsErrors>False</TreatWarningsAsErrors>
  <NoWarn>1701;1702;S1135</NoWarn>
</PropertyGroup>

Can you please provide more information on how to reproduce the issue?

11

Hmm, something very strange is happening: it works in one project, but doesn’t in another, both in the same solution. I will continue investigating

12

I think we may override the project-defined diagnostic options with the ones from the Quality Profile. I will keep you updated on.

13

@HamsterExAstris could you please try this build to verify that it fixes the problem for you? SLVS-2825 Respect user overrides for issue severities · SonarSource/sonarlint-visualstudio@2c7bacb · GitHub

14

@georgii.borovinskikh Looks good to me - confirmed I’m no longer seeing the issues that should be suppressed, and when I introduce other issues to the code they are still flagged as expected.

2 Likes
15

Thanks. I merged it, will be part of the next release.

2 Likes