Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

 

"Sonar.UnknownIssueType" Violation

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 I've populated the SonarQube rule repository using these values.  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.

  

Image Added

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.

Change Log

...