|Latest version||0.1 ( Unreleased )|
|Requires SonarQube version||3.0 or higher |
|Download||(release not yet available – try the CI builds instead)|
|License||GNU LGPL 3|
|Developers||John M. Wright (Twitter) (Blog)|
Description / Features
The .NET ReSharper plugin supports using the free JetBrains ReSharper command line code inspection tool "InspectCode" as a source for .NET-based static analysis issues. ReSharper is an extremely popular commercial plugin to the Visual Studio IDE for .NET development and this plugin allows users to have a parallel experience in the IDE and in SonarQube when it comes to code analysis results.
What You Can Expect To See
Something like this in Visual Studio using ReSharper:
Will turn into this in SonarQube:
- The .Net Ecosystem plugins (C# Ecosystem and/or the VB.NET plugin), version 2.1 or greater
- The JetBrains ReSharper command line tools
- There are consistency issues in versions of the tools before 8.1, so I recommend using the 8.1 Beta builds (or GA version, once released)
- Install the .NET and C# plugins following their installation instructions
- Install the sonar-dotnet-resharper-plugin from the Update Center or download them (link at top of this page) into the SONARQUBE_HOME/extensions/plugins directory
- Restart the SonarQube server
- Modify Your Project's Quality Profile (see below)
Modify Your Project’s Quality Profile
If you install the sonar-dotnet-resharper-plugin on a clean system where you have not modified the “Sonar way” Quality Profile, then all of the new ReSharper-based rules will be included and enabled immediately. However, if you have modified that profile or have your own custom profile(s), you will need to enable the ReSharper rules for that profile after installing the plugin. To do this, go into the SonarQube web UI, click the “Quality Profiles” link in the header bar, and choose the profile you wish to include ReSharper results.
In the filter boxes, choose “ReSharper” in the Repository field and “Any” from the Activation field and click "Search". I expect you’ll see a list of approx 650 rules, all disabled. In the upper right corner of the results list is a “Bulk Change” option. Choose “Activate all”. This will (immediately) activate all of the ReSharper rules for this profile.
Running an Analysis
Now, add the following properties to your sonar-project.properties file(s) based on which scenario you wish to follow.
Where the value of
sonar.resharper.reports.path is the path to the ReSharper results file relative to each project file, as an absolute path, or utilize any of the Path Patterns supported by the .Net ecosystem plugins. This has the current limitation (same as the FxCop and other sonar-dotnet plugins) of requiring the same relative path be used for all projects. As such, if your filesystem layout has project files at different depths relative to the results file, you should consider using an absolute path or one of the Path Patterns.
A Note About Rule Severity
ReSharper users a four-tier severity, while SonarQube uses a five-tier system. I have mapped the ReSharper values like this:
|Do Not Show||Info|
While some of the ReSharper rules are marked as "Do Not Show" by default, the plugin maps them to "Info" so that you can modify their visibility via the Quality Profile. If you want them to not show, disable the rules in the Quality Profile. You can, of course, change any of these levels for any rule using the Quality Profile, and I fully expect most people will want to downgrade a lot of the ‘Critical’ rules to ‘Major’ and a lot of 'Info' to be turned off.
Known Issues / Limitations
The ReSharper command line tools are fairly new and still have a few kinks to work out. Versions before 8.1 are not recommended, as several key issues were addressed in the 8.1 release.
Inconsistent results from inspectcode
From one run to the next, you may get a different list of rule violations from ReSharper, even without code changes: See http://youtrack.jetbrains.com/issue/RSRP-390005 UPDATE: This has been marked as "fixed" as of version 126.96.36.199 (2013-11-30)
SonarQube requires that the rule database be populated up front, at server start. ReSharper provides a list of possible violation types for their tool via the `/dumpIssuesTypes` argument, and the plugin will populate the SonarQube rule repository using these values (as of the plugin's build). However, as new versions come out, or you add your own ReSharper plugins to generate new IssueTypes, it’s possible that you will have violations in your code that the plugin did not know about when the server started, so cannot import into SonarQube appropriately. When the plugin comes across one of these, it will write a log statement (to the runner’s log) and generate a "Sonar.UnknownIssueType" violation with instructions on how to add the rule information to the 'ReSharper custom rules' property in the Settings UI. After adding that setting and restarting SonarQube, future analysis runs will support those IssueTypes.
Other File Types
While the ReSharper tools support the full .Net stack, including .xaml and other file types, The sonar-dotnet API does not currently support more than one language (C# or VB.net) for a given project. For .xaml and other files, the plugin attempts to report the violation against the file, but they may end up attached to the project instead. In either case, the source code for the .xaml or other unsupported file type will not be imported into SonarQube.
|SONARPLUGINS-3355||Empty/default RunMode causes NPE||Dec 23, 2013||Jan 20, 2014||John Wright||John Wright||Closed||Fixed|
|SONARPLUGINS-3331||pom uses incorrect groupId||Dec 06, 2013||Dec 12, 2013||John Wright||John Wright||Closed||Fixed|
|SONARPLUGINS-3305||make wiki links clickable||Dec 03, 2013||Dec 03, 2013||John Wright||John Wright||Closed||Fixed|
|SONARPLUGINS-3269||provide means to enable/disable violation creation for files ignored by .net plugin||Nov 20, 2013||Dec 03, 2013||John Wright||John Wright||Closed||Fixed|
|SONARPLUGINS-3261||RunMode values not respected||Nov 16, 2013||Dec 03, 2013||John Wright||John Wright||Closed||Fixed|
|SONARPLUGINS-3234||When using 'reuseReport' mode, plugin should verbosely fail if file not found||Oct 31, 2013||Dec 03, 2013||John Wright||John Wright||Closed||Fixed|
|SONARPLUGINS-3233||report path property behavior differs from other .NET plugins||Oct 31, 2013||Dec 12, 2013||John Wright||John Wright||Closed||Fixed|
|SONARPLUGINS-3202||Utilize new inspectcode "dumpIssueTypes" flag to populate rules||Oct 28, 2013||Dec 03, 2013||John Wright||John Wright||Closed||Fixed|
|SONARPLUGINS-3200||File paths associated with violations are incorrect (duplicate project folder)||Oct 24, 2013||Dec 03, 2013||John Wright||John Wright||Closed||Fixed|