Discover and update the VB.NET-specific properties in: Administration > General Settings > 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 > Administration > General Settings > VB.NET. By default, tool-generated code files are skipped from analysis.
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.
To analyze VB.NET code, you need to use the SonarScanner for MSBuild version 4.x or newer.
- Importing External Issues (VSTest, NUnit, MSTest, xUnit)
- Test Coverage & Execution (Visual Studio Code Coverage, dotCover, OpenCover, NCover 3)
- SonarScanner for MSBuild
- SonarScanner for Azure DevOps
Check the issue tracker for this language.