Resharper Visual Studio 2019 How To Do This

It seems both Microsoft and JetBrains are not happy with Visual Studio performing essentially the same code parsing twice all the time, as evidenced by: (a) Visual Studio telling you Resharper just took 45 seconds to load and bugging you to get rid of slow plugins (b) JetBrains starting their own C IDE (Project Rider) so they arent bogged down with VS slowness Personally, if I can get everything out of the box with Visual Studio and I no longer need Resharper then in my eyes thats 1 less thing to install and manage, but right now there are still many refactoring tools missing from Visual Studio which makes Resharper still very useful.

Resharper Visual Studio 2019 How To Do This

I recently had to figure out how to do this myself and was amazed at the lack of clarity online not only how many different options there were, but many of the articles are now out of date as the tech has moved on.

TL:DR: I used StyleCop first, using StyleCop.Analyzers nuget package, and automatically added it to all projects.

Create a Directory.Build.props file next to your solution, looks like this: (SolutionDir)StyleCop.ruleset 2.

Create a StyleCop.ruleset file next to your solution, looks like this: (Feel free to customise the rules) 3.

OPTIONAL) Create a stylecop.json file next to your solution, looks like this: schema:, settings: orderingRules: usingDirectivesPlacement: outsideNamespace This file is to customise the rule behaviour (NOT to enabledisable rules).

This is an alternative to simply disabling the rule.

Thats it:) StyleCop will now lint your code on build (NOTE: It will only lint the code that has changed since the last rebuild).

In Visual Studio you can press Alt F11 to lint the entire solution.

Fixing linting errors StyleCop as above comes with a sibling nuget package called StyleCop.Analyzers.CodeFixes which allows Visual Studio (and probably VS Code and others) to provide user prompts to automatically fix errors.

Note that these menu fixes typically come with a fix all in solution button which will fix the linting error across the whole solution: The full list of which errors have automatic solutions coded is listed here StyleCop To use StyleCop in 2019 you simply install the nuget package StyleCop.Analyzers.

You can do this on a per-project basis or globally (as above) using Directory.Build.props.

Once youve installed the nuget package you will start getting warnings for things you dont care about, and will want to disable rules.

The documentation for disabling rules tells you to use the Visual Studio UI, but Ive found this useless at dealing with a solution-level ruleset file.

If you use Visual Studio to Suppress a rule, it typically gives you the options: In Source ( pragma warning disable) In Suppression file ( GlobalSuppressions.cs ) Ideally there would be a In Ruleset file option, but this isnt implemented.

I opened a feature request for it here ) To add it to your global ruleset file, you must do it manually Ive had to manually write out XML lines to suppress rules.

Please let me know if theres an automated solution Ive missed Here is a gist to show what a file looks like.

Just right click - Open With - XML Text Editor, and save yourself the pain The whole system is quite flexible, so for example you can have different ruleset files for different projects (maybe one for test projects, one for production code) and you have even reference more than one and they override each others settings based on the order you reference them.

If you want to enable StyleCop on just some projects then either directly reference the.ruleset file from your.csproj files or reference a.props file from your.csproj file that references the.ruleset file.

Sonar Sonar is, IMO, not a competitor to Stylecop, it is designed for a different purpose and can be used alongside Stylecop.

It does deeper analysis of your code than stylecop, so it is (warning: over-generalisation) less concerned with where you put your braces and more concerned with cyclomatic complexity.

You can use both.

Sonar does NOT have automatic fixes for its errors, which might annoy some people as it purely tells you whats wrong, but doesnt help you fix it.

Sonar DOES have the ability to rate your code cleanliness, host a central server, track your code over time by integrating into CI.

If you want a simple linter with automatic fixes, StyleCop is what you want.

If you want a higher level tracking system for how complex your codebase is over time, and maybe even comparing codebases between teams, and tracking technical debt, Sonar is what you want.

Resharper Resharper provides a free command line tool to lint your code.

So this is a paid solution and requires everyone on your team to be licensed.

I wont cover the resharper setup because my team is not licensed for it.

In you are a Resharper fan (as a lot of C developers are) bear in mind that Microsoft are providing more and more Resharper functionality in Visual Studio, Roslyn, and related tooling, so its worth keeping an eye on how Microsoft progresses in this area, and also how much Resharper slows down Visual Studio, how much it costs etc.