Skip to end of metadata
Go to start of metadata

By SonarSource – SonarSource – Issue Tracker – Supported by SonarSource
More versions
SonarVB 4.2 – Dec 11, 2017 – SonarQube 6.7+ (Compatible with LTS)
Support for .NET core and shared files
I accept the Terms and ConditionsDownloadRelease notes


Enables the powerful SonarVB analyzer.

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.

  1. Install SonarQube Server (see Setup and Upgrade for more details)
  2. Install SonarQube Scanner for MSBuild and be sure your can call SonarQube.Scanner.MSBuild.exe from the directory where you have your source code
  3. Install SonarVB (see Installing a Plugin for more details). 
  4. Run your analysis by executing the following commands from the root directory of the project:

    SonarQube.Scanner.MSBuild.exe begin /k:"org.sonarqube:sonarqube-scanner-msbuild" /n:"Project Name" /v:"1.0"
    MSBuild.exe /t:Rebuild
    SonarQube.Scanner.MSBuild.exe end
  5. Follow the link provided at the end of the analysis to browse your project's quality in the SonarQube UI.

Advanced Usage

With SonarVB, you can:

Known Limitations

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 multiple spaces, the string 'error', zero or multiple 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.

  • No labels