# SonarScanner for .NET

Since version 5.0, the SonarScanner for MSBuild is now the SonarScanner for .NET. Documentation is updated with that new name, artifacts and links will remain with the old name for now.

The SonarScanner for .NET is the recommended way to launch an analysis for projects/solutions using MSBuild or dotnet command as a build tool. It is the result of a collaboration between SonarSource and Microsoft.

SonarScanner for .NET is distributed as a standalone command line executable, as an extension for Azure DevOps Server, and as a plugin for Jenkins.

It supports .Net Core on every platform (Windows, macOS, Linux).

## Prerequisites

The flavor used to compile the Scanner for .NET (either .NET Framework, .NET Core or .NET) is independent of the .NET version the project you want to analyze has been built with. Concretely, you can analyze .NET Core code with the .NET Framework version of the Scanner. It's only relevant depending on your OS, and on the versions of .NET SDKs that are installed on your build machine.

### Compatibility

Scanner VersionSonarQube
5.xLTS 6.7+
4.xLTS 6.7+

## Installation

### Standalone executable

• Expand the downloaded file into the directory of your choice. We'll refer to it as $install_directory in the next steps. • On Windows, you might need to unblock the ZIP file first (right-click file > Properties > Unblock). • On Linux/OSX you may need to set execute permissions on the files in $install_directory/sonar-scanner-(version)/bin.
• Uncomment, and update the global settings to point to your SonarQube server by editing $install_directory/SonarQube.Analysis.xml. Values set in this file will be applied to all analyses of all projects unless overwritten locally. Consider setting file system permissions to restrict access to this file.: <SonarQubeAnalysisProperties xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.sonarsource.com/msbuild/integration/2015/1"> <Property Name="sonar.host.url">http://localhost:9000</Property> <Property Name="sonar.login">[my-user-token]</Property> </SonarQubeAnalysisProperties>  • Add $install_directory to your PATH environment variable.

### .NET Core Global Tool

dotnet tool install --global dotnet-sonarscanner --version x.x.x


The --version argument is optional. If it is omitted the latest version will be installed. Full list of releases is available on the NuGet page

.NET Core Global Tool is available from .NET Core 2.1+

### On Linux/OSX, if your SonarQube server is secured

1. Copy the server's CA certs to /usr/local/share/ca-certificates
2. Run sudo update-ca-certificates

## Use

You can invoke the Scanner using arguments with both dash (-) or forward-slash (/) separators. Example : SonarScanner.MSBuild.exe begin /k:"project-key" or SonarScanner.MSBuild.exe begin -k:"project-key" will work.

There are two versions of the SonarScanner for .NET. In the following commands, you need to pass an authentication token using the sonar.login property.

### "Classic" .NET Framework Invocation

The first version is based on the "classic" .NET Framework. To use it, execute the following commands from the root folder of your project:

SonarScanner.MSBuild.exe begin /k:"project-key" /d:sonar.login="<token>"
MSBuild.exe <path to solution.sln> /t:Rebuild


Note: On macOS or Linux, you can also use mono <path to SonarScanner.MSBuild.exe>.

### .NET Core and .NET Core Global Tool Invocation

The second version is based on .NET Core which has a very similar usage:

dotnet <path to SonarScanner.MSBuild.dll> begin /k:"project-key" /d:sonar.login="<token>"
dotnet build <path to solution.sln>
dotnet <path to SonarScanner.MSBuild.dll> end /d:sonar.login="<token>"


The .NET Core version can also be used as a .NET Core Global Tool. After installing the Scanner as a global tool as described above it can be invoked as follows:

dotnet tool install --global dotnet-sonarscanner
dotnet build <path to solution.sln>


In summary, the invocation of the SonarScanner for .NET will depend on the scanner flavor:

Scanner FlavorInvocation
.NET 5dotnet <path to SonarScanner.MSBuild.dll> etc.
.NET Core Global Tooldotnet sonarscanner begin etc.
.NET Core 2.0+dotnet <path to SonarScanner.MSBuild.dll> etc.
.NET Framework 4.6+SonarScanner.MSBuild.exe begin etc.

Notes:

• The .NET Core version of the scanner does not support TFS XAML builds and automatic finding/conversion of Code Coverage files. Apart from that, all versions of the Scanner have the same capabilities and command line arguments.

## Analysis steps

### Begin

The begin step is executed when you add the begin command line argument. It hooks into the build pipeline, downloads SonarQube quality profiles and settings and prepares your project for the analysis.

Command Line Parameters:

ParameterDescription
/k:<project-key>[required] Specifies the key of the analyzed project in SonarQube
/n:<project name>[optional] Specifies the name of the analyzed project in SonarQube. Adding this argument will overwrite the project name in SonarQube if it already exists.
/v:<version>[recommended] Specifies the version of your project.
/d:sonar.login=<token> or <username>[recommended] Specifies the authentication token or username used to authenticate with to SonarQube. If this argument is added to the begin step, it must also be added to the end step.
/d:sonar.password=<password>[optional] Specifies the password for the SonarQube username in the sonar.login argument. This argument is not needed if you use authentication token. If this argument is added to the begin step, it must also be added on the end step.
/d:sonar.verbose=true[optional] Sets the logging verbosity to detailed. Add this argument before sending logs for troubleshooting.
/d:sonar.dotnet.excludeTestProjects=true[optional] Excludes Test Projects from analysis. Add this argument to improve build performance when issues should not be detected in Test Projects.
/d:<analysis-parameter>=<value>[optional] Specifies an additional SonarQube analysis parameter, you can add this argument multiple times.

For detailed information about all available parameters, see Analysis Parameters.

The "begin" step will modify your build like this:

• the active CodeAnalysisRuleSet will be updated to match the SonarQube quality profile
• WarningsAsErrors will be turned off

If your build process cannot tolerate these changes we recommend creating a second build job for SonarQube analysis.

### Build

Between the begin and end steps, you need to build your project, execute tests and generate code coverage data. This part is specific to your needs and it is not detailed here.

### End

The end step is executed when you add the "end" command line argument. It cleans the MSBuild/dotnet build hooks, collects the analysis data generated by the build, the test results, the code coverage and then uploads everything to SonarQube

There are only two additional arguments that are allowed for the end step:

ParameterDescription
/d:sonar.login=<token> or <username>This argument is required if it was added to the begin step.
/d:sonar.password=<password>This argument is required if it was added to the begin step and you are not using an authentication token.

### Known Limitations

• MSBuild versions older than 14 are not supported.
• Web Application projects are supported. Legacy Web Site projects are not.
• Projects targeting multiple frameworks and using preprocessor directives could have slightly inaccurate metrics (lines of code, complexity, etc.) because the metrics are calculated only from the first of the built targets.

## Code Coverage

In a Azure DevOps / TFS environment, test files are automatically retrieved following this search

• Search for .trx files in any TestResults folder located under the $Build.SourcesDirectory path • If not found, then a fallback search is made against$Agent.TempDirectory

Once trx files have been found, their .coverage counterpart are searched as well and the scanner tries to convert them to .coveragexml files that will be uploaded to SonarQube. CodeCoverage.exe tool is used for that, and the scanner also needs to find a path to that tool, following this search path

• Search for the presence of VsTestToolsInstallerInstalledToolLocation environment variable, set by the VsTestToolsPlatformInstaller task or by the user
• If not found, search for either the presence of that tool in well-known installation path, or via the registry.

As stated above, this will work only with the .NET 4.6 flavor of the Scanner.

## Excluding projects from analysis

Some project types, such as Microsoft Fakes, are automatically excluded from analysis. To manually exclude a different type of project from the analysis, place the following in its .xxproj file.

<!-- in .csproj -->
<PropertyGroup>
<!-- Exclude the project from analysis -->
<SonarQubeExclude>true</SonarQubeExclude>
</PropertyGroup>


Analyzing MSBuild 12 projects with MSBuild 14
The Sonar Scanner for .NET requires your project to be built with MSBuild 14.0. We recommend installing Visual Studio 2015 update 3 or later on the analysis machine in order to benefit from the integration and features provided with the Visual Studio ecosystem (VSTest, MSTest unit tests, etc.).

Projects targeting older versions of the .NET Framework can be built using MSBuild 14.0 by setting the "TargetFrameworkVersion" MSBuild property as documented by Microsoft:

If you do not want to switch your production build to MSBuild 14.0, you can set up a separate build dedicated to the SonarQube analysis.

Detection of test projects

You can read a full description on that subject on our wiki here.

Per-project analysis parameters Some analysis parameters can be set for a single MSBuild project by adding them to its .csproj file.

<!-- in .csproj -->
<ItemGroup>
<SonarQubeSetting Include="sonar.stylecop.projectFilePath">
<Value>\$(MSBuildProjectFullPath)</Value>
</SonarQubeSetting>
</ItemGroup>


Analyzing languages other than C# and VB

By default, SonarScanner for .NET will only analyze C# and VB files in your project. To enable the analysis of other types of files, these files must be listed in the MSBuild project file (the .csproj or .vbproj file).

More specifically, any files included by an element of one of the ItemTypes in this list will be analyzed automatically. For example, the following line in your .csproj or .vbproj file

<Content Include="foo\bar\*.js" />


will enable the analysis of all JS files in the directory foo\bar because Content is one of the ItemTypes whose includes are automatically analyzed.

You can also add ItemTypes to the default list by following the directions here.

You can check which files the scanner will analyze by looking in the file .sonarqube\out\sonar-project.properties after MSBuild has finished.

Using SonarScanner for .NET with a Proxy
On build machines that connect to the Internet through a proxy server you might experience difficulties connecting to SonarQube. To instruct the Java VM to use the system proxy settings, you need to set the following environment variable before running the SonarScanner for .NET:

SONAR_SCANNER_OPTS = "-Djava.net.useSystemProxies=true"


To instruct the Java VM to use specific proxy settings or when there is no system-wide configuration use the following value:

SONAR_SCANNER_OPTS = "-Dhttp.proxyHost=yourProxyHost -Dhttp.proxyPort=yourProxyPort"


Where yourProxyHost and yourProxyPort are the hostname and the port of your proxy server. There are additional proxy settings for HTTPS, authentication and exclusions that could be passed to the Java VM. For more information see the following article: https://docs.oracle.com/javase/8/docs/technotes/guides/net/proxies.html.

HTTP_PROXY, HTTPS_PROXY, ALL_PROXY and NO_PROXY will be automatically recognized and used to make calls against SonarQube. The Scanner for .NET makes HTTP calls, independant from the settings above concerning the Java VM, to fetch the Quality Profile and other useful settings for the "end" step.

## Known issues

I have multiple builds in the same pipeline, each of them getting analyzed even if the Run Code Analysis has already been executed

We don't uninstall the global ImportBefore targets to support concurrent analyses on the same machine. Main effect is that if you build a solution where a .sonarqube folder is located nearby, then the sonar-dotnet analyzer will be executed along your build task.

To avoid that, you can disable the targets file by adding a build parameter:

msbuild /p:SonarQubeTargetsImported=true
dotnet build -p:SonarQubeTargetsImported=true