Hi Julien, thanks for your reply. If I’m not mistaken, the current approach is to add the analyzer to every project. We have a very large Legacy app, and modern and new bits around this legacy application. There are many solutions and a ton of projects.
We need the connected mode to easily manage rules across such a diverse code base, with multiple teams (legacy/customizing/modernization) having very different rules that are enforced by SonarQube.
There are build processes and sonar qube analyzers running on our build servers.
Due to the complex nature of the matter, even the JetBrains annotation package is sometimes causing issues on our build agents.
The reported issues from SonarQube are complimentary to Riders inspections. We use both on our build servers. While a few reported code smells conflict between rider and sonarlint they mostly focus on other things. The code smell reports of the roslyn analyzers work just fine, and as expected, and the impact on the IDE seemed fine (but I only tested it on a small portion).