I’ve read in some forum posts that https://github.com/SonarSource/sonarqube-roslyn-sdk has been deprecated. I am responsible among other things for managing sonarqube instances for our customers and colleagues, and we use the sonarqube roslyn sdk to add some extra rules such as https://security-code-scan.github.io/ to our sonarqube instances so our customers don’t need to add them to all their projects.
Is there any alternative you guys offer for our use case? Adding these rules is a value add for the service we provide for our customers.
Also if the sonarqube roslyn sdk is deprecated perhaps you should add that to the readme on the git repo, because people are still adding issues and pull requests.
Hi @Rouke.Broersma.IS - out of curiosity, could you please tell us what forums you read that the Roslyn SDK has been deprecated?
As you can see here:
The SonarQube Roslyn SDK is not deprecated. However, it is true it does not get a lot of our attention and we are discussing internally what we should do with it in the future.
I am mainly asking because we need this pr merged to be able to keep using sq roslyn sdk as we provide services on linux now as well as windows, and the linked issue is blocking for linux support:
Is the Sdk working for SonarQube 8.x? As some SonarQube API of 6.x was now removed and the Sdk v2.0 generates Plugins compatible from 6.7 the plugins will (or have already) break.
We would also welcome to continue using the Sdk with current Roslyn analzers.
Do you have an update for this sdk yet? It hasn’t had a new release for over 2 years now, its getting out of date with the latest Visual Studio changes, for example these:
And as far as I can tell SonarQube also doesn’t support the EditorConfig configuration files for Rosyln analysers.
Is this just an overall dropping of support for Visual Studio?
@Andrei_Epure thanks for the update, is there a guide on how to import EditorConfig into SonarQube? I can’t find anything related to how I define .EditorConfig in SonarQube, or how to get SonarLint to consume it and apply the defined config.
.editorconfig files are picked out of the box by Roslyn during the build and applied by Roslyn when running the analysis. And the Scanner for .NET imports the output of the Roslyn analysis during the build. Note: our analyzers are Roslyn analyzers and are thus integrated during the msbuild compilation.
So, for example, you can exclude a SonarQube rule for a particular file using editorconfig - see SonarQube docs.
We do this so we can sync rulesets across repositories. As far as I can tell SonarQube only publishes the old style ruleset as xml, not as EditorConfig?