SonarScanner for MSBuild
The SonarScanner for MSBuild 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.
It supports .Net Core multi-platform projects and it can be used on non-Windows platforms.
- At least the minimal version of Java supported by your SonarQube server
The SDK corresponding to your build system:
- .NET Framework v4.6+ - either Build Tools for Visual Studio 2015 Update 3 or the Build Tools for Visual Studio 2017
- .NET Core 2.0 - .NET Core SDK 2.0 (for .NET Core version of the scanner)
- .NET Core 2.1 - NET Core SDK 2.1.3 (for .NET Core version of the scanner or if you plan to use .NET Core Global Tool
SonarScanner for MSBuild for .NET Framework or .NET Core
Expand the downloaded file into the directory of your choice. We'll refer to it as
$install_directoryin the next steps.
- On Windows, you might need to unblock the ZIP file first (Right click on file > Properties > Unblock).
- On Linux/OSX you may need to set execute permissions on the files in
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>
$install_directoryto your PATH environment variable.
Installation of the SonarScanner for MSBuild .NET Core Global Tool
dotnet tool install --global dotnet-sonarscanner --version 4.3.1
The --version argument is optional. If it is omitted the latest version will be installed.
On Linux/OSX, if your SonarQube server is secured:
- Copy the server's CA certs to
There are two versions of the SonarScanner for MSBuild.
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" MSBuild.exe <path to solution.sln> /t:Rebuild SonarScanner.MSBuild.exe end
Note: On Mac OS or Linux, you can also use
mono <path to SonarScanner.MSBuild.exe>.
The second version is based on .NET Core which has a very similar usage:
dotnet <path to SonarScanner.MSBuild.dll> begin /k:"project-key" dotnet build <path to solution.sln> dotnet <path to SonarScanner.MSBuild.dll> end
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 sonarscanner begin /k:"project-key" dotnet build <path to solution.sln> dotnet sonarscanner end
- The .NET Core version of the scanner does not support TFS XAML builds. Apart from that, the two versions of scanner have the same capabilities and command line arguments.
- Single .NET Core project files (csproj or vbproj) could be built and successfully analyzed only if a
<ProjectGuid>unique guid</ProjectGuid>element is added in the csproj or vbproj XML. The
<ProjectGuid>element is not required if you build a solution (sln) containing that project.
The begin step is executed when you add the
begin command line argument. It hooks into the MSBuild pipeline, downloads SonarQube quality profiles and settings and prepares your project for the analysis.
Command Line Parameters:
||[required] Specifies the key of the analyzed project in SonarQube|
||[optional] Specifies the name of the analyzed project in SonarQube. Adding this argument will overwrite the project name in SonarQube if it already exists.|
||[recommended] Specifies the version of your project.|
||[optional] Specifies the username or access token to authenticate with to SonarQube. If this argument is added to the begin step, it must also be added on the end step.|
||[optional] Specifies the password for the SonarQube username in the
||[optional] Sets the logging verbosity to detailed. Add this argument before sending logs for troubleshooting.|
||[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
CodeAnalysisRuleSetwill be updated to match the SonarQube quality profile
WarningsAsErrorswill be turned off
If your build process cannot tolerate these changes we recommend creating a second build job for SonarQube analysis.
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.
The end step is executed when you add the "end" command line argument. It cleans the MSBuild 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:
||[optional] This argument is required if it was added to the begin step.|
||[optional] This argument is required if it was added to the begin step and you are not using an authentication token.|
- 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.
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 MSBuild 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
SonarQube analyzes test projects differently from non-test projects, so it is important to correctly classify test projects.
By default, the SonarQube Scanner for MSBuild will detect as test project:
. MSTest unit test projects, thanks to the presence of a well-known project type GUID in .csproj file of such projects.
Projects with names ending in "Test" or "Tests". This behavior can be changed by providing the parameter
sonar.msbuild.testProjectPatternto the begin step (regex follows .NET Regular Expression in a case-sensitive way with the default value
.*Tests?\.(cs|vb)proj$). This regex is applied against the fullname of the
.vbprojwhich is why it's recommended to keep at the end of your custom regex
\.(cs|vb)proj$. To manually classify a project as a test project, mark it with
<!-- in .csproj --> <PropertyGroup> <!-- Mark the project as being a test project --> <SonarQubeTestProject>true</SonarQubeTestProject> </PropertyGroup>
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>
Concurrent Analyses on the Same Build Machine
Concurrent analyses (i.e. parallel analysis of two solutions on the same build machine using a unique service account) are not supported by default by the Scanner for MSBuild. You can enable it as follows:
- Locate the folder containing the Scanner for MSBuild
- Go in the
Targetsfolder and copy the folder
Paste it under your build tool global
ImportBeforefolder (if the folder doesn't exist, create it).
For MSBuild, the path is
<MSBUILD_INSTALL_DIR>\<Version>\Microsoft.Common.targets\ImportBeforewhere <MSBUILDINSTALLDIR> is: *For v14, default path is:
C:\Program Files (x86)\MSBuild\14.0\Microsoft.Common.Targets\ImportBefore
- For v15, default path is:
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Microsoft.Common.targets\ImportBefore(for VS Community Edition)
- For v16, default path is:
C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Microsoft.Common.targets(for VS Community Edition)
- For v15, default path is:
- For dotnet, the path is
<DOTNET_SDK_INSTALL_DIR>can be found using the
dotnet --infoand looking for the Base Path property.
The performance impact of this global installation for projects that aren't analyzed is negligible as this target is only a bootstrapper and will bail out nearly instantaneously when the
.sonarqube folder is not found under the folder being built.
Using SonarScanner for MSBuild 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 MSBuild:
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 full reference visit the following article: https://docs.oracle.com/javase/8/docs/technotes/guides/net/proxies.html