SonarLint for Visual Studio: v6.0 - Sync C# and VB.NET SonarQube and SonarCloud issue suppressions

Dear .NET developers,

If you work in a team, or if by any other means you are several developers working on the same project, you probably know how important it is to agree on a common definition of code quality and security standards for your code. This is why, with the connected mode, SonarLint offers a way to automatically sync the quality profile defined in SonarQube or SonarCloud for your project, so that it is easily effortlessly applied in every contributor’s IDE.

What’s more, when you use SonarLint in connected mode, you benefit of the synchronization of issue suppressions. This means that, if someone in your team marks an issue detected by SonarQube or SonarCloud as “Won’t Fix”, SonarLint will also stop reporting the same issue in your IDE. This is also useful to kill the noise in the (hopefully rare) event that we raise a False Positive.

Unfortunately, while this mechanism was working fine for C and C++ code, there were a few issues some of you reported preventing in some cases, even intermittently, this mechanism from working correctly for C# and .NET code (you can learn more in this ticket).

With this new release we’ve fixed those issues, so that you can use connected mode in Visual Studio to reliably synchronize any issue suppression applied by you or other contributors in SonarQube and SonarCloud.

Last but not least, I’d like to remind our users running old Visual Studio versions that we’ve recently dropped support for Visual Studio 2017, and starting from March the 1st, SonarLint only ships new versions for Visual Studio 2019 and 2022 - to be more precise the minimum Visual Studio 2019 supported is version 16.3.

You can read more in our release notes.