Operating system: Windows 10+11 (not expected to be relevant)
Visual Studio version: VS2022
SonarLint plugin version: 7.X
Programming language: several, mainly C# (not expected to be relevant)
Connected to SonarQube (self-hosted) 10.2.1 (version not expected to be relevant)
With V7 the plugin has switched the configuration of binding information. The files were moved out of source control. The migration is described at Migrate Connected Mode - Visual Studio
Why do you think, that having binding information out of source control is the better solution overall? You are stating that this “makes binding a solution for the first time much simpler because no source-controlled files will be modified”. We (my company) totally disagree!
In the past we could ensure that a solution which is used by a large team is configured correctly regarding binding to the SonarQube server. All users can start using SonarLint within the Solution. No further action is required.
Now, all developers need to take care the binding and (maybe) also when updating the Quality Profile.
Hello @lg2de ,
the reasoning for moving the connected mode configuration out of source control is outlined here.
In the past we could ensure that a solution that is used by a large team is configured correctly regarding binding to the SonarQube server. All users can start using SonarLint within the Solution. No further action is required.
Thanks for sharing this! We indeed received other similar feedback, and we’ve decided to officially support this workflow by adding a possibility to share the connected mode information (namely the server URL and project key) via source control. This will not happen automatically to avoid generating noise but it will be an option available via the Extensions menu.
We’re going to release this in version 7.4, which should be released in a matter of days.
Hi Marco, would you happen to know if a similar Workflow for sharing the configuration is already present in SonarLint for IntelliJ or Eclipse? If not: it totally would be a boon there, too (i did not start a research for smth like that yet, but i know it would support some setups we try to maintain)
Hi @daniel,
it is not supported yet. We’re launching this in Visual Studio first, and we’ll potentially extend the same possibility to IntelliJ, Eclipse and VS Code. You can follow this roadmap card to get the updates.
ty for the prompt reply and tyvm for linking the roadmap card. it contained another equally relevant referenced roadmap card!
i hope i am not derailing lukas OP too much but: is there anything which you maybe could link to, that fleshes out how you would like to implement referenced roadmap card? e.g.: source-control-based, or sq-server-based or maybe smth that would need to be installed/configured inside the ide/sonarlint installation?
You are welcome, Daniel! You are just even faster than me…
I hope for a solution which is compatible for all IDEs. We are currently using Visual Studio and Rider in parallel. Both should be bound the project WITHIN the source control to be synchronized for all developers.
We did not dig too much into that just yet, and suggestions are very welcome I believe automating the deployment of credentials is something valuable for organizations, but TBH this is something under consideration, meaning we don’t have an ETA for now and we have not started exploring the possible solutions.
(i did not start a research for smth like that yet, but i know it would support some setups we try to maintain)
I believe automating the deployment of credentials is something valuable for organizations, but TBH this is something under consideration, meaning we don’t have an ETA for now and we have not started exploring the possible solutions.