# VB.NET

## Language-specific properties <a href="#language-specific-properties" id="language-specific-properties"></a>

Discover and update the VB.NET-specific [Analysis parameters](/sonarqube-server/8.9/analyzing-source-code/analysis-parameters.md) in **Administration > General Settings > VB.NET**.

### Analyze generated code <a href="#analyze-generated-code" id="analyze-generated-code"></a>

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.

## Known limitations <a href="#known-limitations" id="known-limitations"></a>

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](https://github.com/dotnet/roslyn/issues/5724/)). In order to work around this problem, analysis will skip issues reported on any line where the pattern is detected.

## Scanner compatibility <a href="#scanner-compatibility" id="scanner-compatibility"></a>

To analyze VB.NET code, you need to use the [SonarScanner for .NET](/sonarqube-server/8.9/analyzing-source-code/scanners/sonarscanner-for-dotnet.md) version 4.x or newer.

## Related Pages <a href="#related-pages" id="related-pages"></a>

* [Importing third-party issues](/sonarqube-server/8.9/analyzing-source-code/importing-external-issues/importing-third-party-issues.md) (VSTest, NUnit, MSTest, xUnit)
* [Test coverage and execution](/sonarqube-server/8.9/analyzing-source-code/test-coverage-and-execution.md) (Visual Studio Code Coverage, dotCover, OpenCover, NCoverlet 3)
* [SonarScanner for .NET](/sonarqube-server/8.9/analyzing-source-code/scanners/sonarscanner-for-dotnet.md)
* [SonarScanner for Azure DevOps](/sonarqube-server/8.9/analyzing-source-code/scanners/sonarscanner-for-azure-devops.md)

## Issue tracker <a href="#issue-tracker" id="issue-tracker"></a>

Check the [issue tracker](https://github.com/SonarSource/sonar-dotnet/issues) for this language.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sonarsource.com/sonarqube-server/8.9/analyzing-source-code/languages/vb-dotnet.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.