Rider support for SonarLint

[alexeyzimarev]

JetBrains Rider is a popular alternative to Visual Studio that got a lot of traction among .NET developers. Those who use Mac and Linux mostly use Rider when developing for .NET. It is very unfortunate that SonarLint IntelliJ plugin doesn’t include Rider in the list of supported Jetbrains IDEs.

Previously, it was pointed out that the lack or Roslyn analyzers support in Rider prevent this feature to be included in SonarLint, but this blocker is now removed https://groups.google.com/forum/#!topic/sonarlint/pgmvXyVt-6I

Please consider extending SonarLint plugin for JetBrains IDEs to support Rider and C#.

[geik (Guus Eikens)]

Oh yes please!

[Jonatino (Jonathan Beaudoin)]

Would love to see support for Rider. +1

[jlaverty (James Laverty)]

That would be a great addition. +1

[AlexSrizhevskiy]

Hello! any updates?

[univac (Luiz Alexandre Deschamps)]

That would be great, please +1

[Steven_Markey]

We would love to have Rider supported too! Many of our Engineers use Rider as their primary IDE.

[joe_mighty (Joseph Woodward)]

Rider support would be great!

[maurofranchi]

Yes please!

[Gurpal_Sangha]

Yes please !! We have more engineers on Rider than VS in our teams.

[Ed_Courtenay]

+1 for Rider support

[davide (David Edwards)]

+1 for Rider support

[duncanp (Duncan Pocklington)]

Thanks everyone for the feedback and interest in expanding the reach of SonarLint.

The short answer is that it’s something we’d thought about, but weren’t planning on starting anything this year.

Some background: previously SonarLint was handled by a virtual team, all of whom also worked on other products, which made it difficult for us to give SonarLint as much attention as we wanted. To address this, we recently formed a dedicated team and we’re in the process of setting our objectives for the next six months (shameless plug: we’re also expanding the team so if you’re interested in writing IDE extensions have a look at our jobs page :-))

Our short- to mid-term plan is to focus on improving the standalone experience for some of the language/IDE combinations we already ship (e.g. simpler setup, better perf and rules configuration for C++ in VS, setup and perf improvements for TypeScript/JavaScript in VS Code) before adding support for other IDEs.

Having said that, our larger goal is to support major languages like C#, C++, Java etc in the IDEs that are most used by developers in those languages. Threads like this one are useful to help us understand the level of demand for particular IDE/language combinations, so thanks again for the feedback - duly noted.

In the meantime, if you want to the Sonar C#/VB.NET rules in Rider today in standalone mode you can add them as NuGet packages/analyzer references as described in the Rider docs. The package ids are SonarAnalyzer.CSharp and SonarAnalyzer.VisualBasic respectively

Thanks,
Duncan

[rider_on_the_storm]

Is the statement above still relevant or did something change in direction Rider?

Would love to see https://www.sonarlint.org/ integrated in Rider as it is for VS.

Please make it happen.

[iangregsondev (Ian Gregson)]

Could somebody give an update to this ?

Rider now support rosyln so its technically possible for it to be integrated into rider ?

[Julien_HENRY]

Thanks for informing us of the Roslyn analyzer support in Rider.

We will have a look, but in the meantime you can try to use our C# analyzer by referencing it as dll in your .csproj file (or use directly the nuget package if you have a .NET Core project):
https://www.jetbrains.com/help/rider/Using_NET_Compiler_Analyzers.html

You can get our analyzer from https://github.com/SonarSource/sonar-dotnet/releases/download/8.2.0.14119/SonarAnalyzer.CSharp.8.2.0.14119.nupkg

Of course you won’t get any advanced SonarLint connected mode features (rule synchronization, …) but this is already a good start.

[Jan_Wf]

Using Rider at work, and Sonarqube on our build server. The connected mode is a must for our large solutions.
Adding roslyn Analyzers the way JetBrains suggests is impractical.

You should consider this.

[Julien_HENRY]

@Jan_Wf

The connected mode is a must for our large solutions.

Out of curiosity, could you be a bit more specific? What are the features you expect the most?

@Jan_Wf

Adding roslyn Analyzers the way JetBrains suggests is impractical.

Even if the setup is impractical, we would be very interested to ear real life feedback about using our C# analyzer in Rider. Does it affect performance? How are reported issues comparing to Rider native inspection (better? duplicate? complimentary ?).
All those feedback will help us to prioritize our efforts.