Visual Studio .slconfig is not getting created or there is no option to create one

SonarQube for IDE Visual Studio
1

Please provide

  • Operating system: Windows 11
  • Visual Studio version: 2022
  • SonarLint plugin version: 8.1.0.95039
  • Programming language you’re coding in: C#
  • Is connected mode used: Yes
    • Connected to SonarCloud or SonarQube (and which version): SonarQube

And a thorough description of the problem / question: I have connected the project (I can see it is showing bound in Team explorer),

But I do not see an option called “Share connected mode configuration”, which I see in IDEs like InteliiJ, VS Code and also it is not getting generated automatically after project binding.

I was expecting it will create a config file needed for visual studio in repo root folder as ./sonarlint/connectedMode.slconfig or ./sonarlint/projectName.slconfig.

I also see in this documentation below lines at Connected Mode - Visual Studio (sonarsource.com)

In SonarLint for Visual Studio version 4.0 and later:

  • The analyzer NuGet packages are no longer installed in any project
  • The settings are saved in a solution-level folder called .sonarlint in a file called [solution name].slconfig.
  1. Can you guys help me how to get this generaged so that I can commit to git.
  2. I also wanted to ask if we can generate connectedMode.json, So that actually I can use it in VS Code. I use VS Code at times and at times Visual Studio.
5

Hi @nithinbanaru
I believe slconfig was deprecated with the version 7.0.

You can share the binding configuration by following the instructions here: Connected Mode setup - Visual Studio

Note, you might need to migrate your connected mode setup to the new format first: Migrate Connected Mode - Visual Studio

8

Hi,

Thanks for the reply. I was able to fix it.
I just want to ask a follow up question related to this itself but I had a different thread and I accidentally marked it as Answered and now not able to ask a follow up question.

Considering the connectivity I am mentioning it here. It would be great if this can be answered.

Other Thread:

Follow Up Question:

Interesting to know that rules can be configured per solution in .NET.

But is it possible to add same Git Repo twice and create 2 projects in SonarQube Cloud? If we can create, I guess its would be generic and can be created by folder scope I guess or there also we have dotnet specific implementation to select solution? If we can’t do such a thing then I don’t see the use of per solution mapping in SolutionName.json right?