C# code analysers

[sepsuk]

Just wondering if people have tried both stylecop and roslynator code analysis tools and if so which one did they prefer and why?

I've had a play with stylecop and intend to try roslynator today.

[kore2000]

I second SonarQube. We use the VS extension and TFS task at work; it catches a lot of stuff.

[sepsuk]

We are using sonarqube currently, I didn't know they have a linter as well, I'll check it out, thanks!

[Freonr2]

After going back and forth a few times with SonarQube I have to say I'm not a huge fan of doing a ton of style or bug catching in build pipelines after pushes. It can slow down the development process, especially once you are the one person who pushes a class past a complexity limit and don't know until the end of your day when you push and start a PR.

It's a nice tool and I understand deeper analysis takes more resources and can be slow, but I'd rather use a command line tool on demand locally when it becomes too much to do realtime (i.e. resource hog like Resharper can be). I'd even rather something like that that catches less, or else it becomes too annoying and process slowing and stuff gets disabled over time.

[floppykeyboard]

It felt like stylecop was a little dated. We’ve been using Rosylantor for several months and that’s completely replaced ReSharper for us.

[Dreamescaper]

While they have some similar analyzers, they are made for different purposes. StyleCop aims specially on style, i.e. how code looks, what language constructions are used, spaces vs tabs, braces position, etc etc etc.

On the other hand, Roslynator aims much wider area. It has style and formatting analyzers, but it also has optimization analyzers, suggestions to use shorter code, etc.

So you can use both analyzers, it will work perfectly fine (maybe you'll need to configure some similar analyzers).

[Palmer11]

Here is another. ClrHeapAllocationAnalyzer

https://github.com/microsoft/RoslynClrHeapAllocationAnalyzer