Steps to Analyze a VB.NET Project
Analyzing a .NET Solution can be done in the Command Line, from Jenkins or from TFS/VSO. Here is a simple and quick example to get started. For more details, please refer to: Analyzing with SonarQube Scanner for MSBuild or consult the sample project on GitHub.
- Install SonarQube Server (see Setup and Upgrade for more details)
- Install SonarQube Scanner for MSBuild and be sure your can call SonarQube.Scanner.MSBuild.exe from the directory where you have your source code
- Install SonarVB (see Installing a Plugin for more details).
Run your analysis by executing the following commands from the root directory of the project:
- Follow the link provided at the end of the analysis to browse your project's quality in the SonarQube UI.
With SonarVB, you can:
Currently an error will be thrown when an issue is raised on a line of code containing the following pattern
\s+error\s*: (i.e. one or more spaces, the string 'error', zero or more spaces and a ':' ) . This is a well known problem on Microsoft side (see issue). In order to work around this problem our analyzer will skip issues reported on any line where the pattern is detected.