VB.NET

VB.NET analysis is available in all editions of SonarQube Server and SonarQube Community Build.

Supported versions

The level of support for a language is defined as follows:

• Fully supported: Analysis will complete. All the language features are understood and examined.
• Supported: Most language features are understood and examined but the version includes unsupported features. Analysis might break or provide incomplete results.

Versions 7 to 16 are fully supported.

Supported frameworks and tools

ASP.NET MVC, ASP.NET Core MVC

Language-specific properties

Discover and update the VB.NET-specific Analysis parameters by going to Administration > Configuration > General Settings > Languages > VB.NET

Analyze generated code

To analyze tool-generated code (e.g. WCF code generated by SvcUtil.exe) for a specific VB.NET project, enable the "Analyze generated code" setting inside Project settings > General Settings > Languages > VB.NET. By default, tool-generated code files are skipped from the analysis.

The detection of generated code is based on file name, special comments, and attributes. The currently recognized values are in GeneratedCodeRecognizer.cs.

When a Generated comment is present in the file, SonarQube ignores the entire ** file, even if only parts of it were generated. It’s possible to enable or disable analysis of files containing generated code at the instance or project level in General Settings > Languages > Your language > Analyze generated code.

Scanner compatibility

To analyze VB.NET code, you need to use the SonarScanner for .NET version 4.x or newer.

Exclusions

Files to be excluded should be set in the project configuration. Excluded files are still going to be analyzed during the compilation and the results will be filtered according to the exclusion settings.

As an alternative, an .editorconfig file can be used to disable the analysis for a specific rule on a file or directory. This can solve performance problems on large files.

[Path/File.vb] dotnet_diagnostic.Sxxx.severity = none

In-line suppression of issues

Standard Roslyn-based suppression mechanisms are available as shown below.

Pragma suppression

#pragma warning disable S2094 // Classes should not be empty S2094
public class Empty { }
#pragma warning restore S2094 // Classes should not be empty S2094

Local SuppressMessage attribute

[SuppressMessage("Major Code Smell", "S2094:Classes should not be empty", Justification = "Because ...")]
public class Empty { }

Global SuppressMessage attribute

// Global Suppression attribute
[assembly: SuppressMessage("Major Code Smell", "S2094:Classes should not be empty", Justification = "Because..", Scope = "member", Target = "~P:SonarAnalyzer.Core.AnalysisContext.Empty.Value")]

Using Visual Studio

The automatic generation of all three suppression mechanisms is supported by standard Visual Studio experience out of the box.

Using SonarQube for Visual Studio

The Pragma suppression mechanism is supported by SonarQube for Visual Studio.

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 more spaces, the string ‘error’, zero or more spaces and a ‘:’ ). This is a well known problem on the Microsoft side (see issue). In order to work around this problem, analysis will skip issues reported on any line where the pattern is detected.

Related Pages

• External analyzer reports (VSTest, NUnit, MSTest, xUnit)
• External analyzer reports (See "Notes on external .NET issues")
• Overview (Visual Studio Code Coverage, dotCover, OpenCover, Coverlet, Altcover)
• Introduction

• Azure DevOps Extension

• Analysis of product projects vs. test projects
• Troubleshooting guide for .NET code coverage import
• Investigating the performance of .NET Analysis