VB.NET
VB.NET analysis is available starting in all editions of SonarQube.
Last updated
Was this helpful?
VB.NET analysis is available starting in all editions of SonarQube.
Discover and update the VB.NET-specific Analysis parameters in Administration > General Settings > VB.NET.
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 .NET version 4.x or newer.
Importing third-party issues (VSTest, NUnit, MSTest, xUnit)
Test coverage and execution (Visual Studio Code Coverage, dotCover, OpenCover, NCoverlet 3)
Check the issue tracker for this language.
Last updated
Was this helpful?
Was this helpful?