This post provides a quick-start guide to using SonarQube to analyze .NET managed code. It covers installing SonarQube locally, running your first analysis using MSBuild, and using some popular third-party analyzers. It also describes how to use the new Visual Studio Online (VSO) and Team Foundation Server (TFS) Build tasks to perform analysis as part of a VSO or TFS build.
[December 18th 2015: How have we done? Details in line on what’s been done, what’s in progress and what’s still being investigated.]
Back in April (2015) we announced our first step in integrating MSBuild and Team Build with SonarQube, At the start of that post,
Today, SonarSource released the MSBuild.SonarQube.Runner 1.0.1, along with the SonarQube C# Plug-in 4.2, and the SonarQube Setup Guide for .NET Users version 1.2.0.
This release contains many bug fixes based on your feedback. The main themes are:
More robust execution,
Note: a more recent documentation is available from Analyzing with SonarQube Extension for VSTS/TFS
[Update Sept 11, 2015: fixing broken links, Thanks Terje!, and adding a Previous post / Next postsection at the end of the post]
As you may be aware,
[Updated August 28th 2015]: If you are using Visual Studio Online, you now have a simpler way of analyzing your .Net code leveraging the Build Tasks for SonarQube Analysis
Release of MSBuild.SonarQube.Runner 1.0
As you might recall, we announced back in April at the //build conference that we were working with SonarSource to provide a better integration of SonarQube with MSBuild and Team Foundation Server.
[23 Sept 2015: See also the SonarQube Integration plans which provides the roadmap for the next months]
[31 August 2015: See also Build Tasks for SonarQube Analysis which provides a summary of the different ways of integrating SonarQube with MSBuild, TFS and Visual Studio Online]
[27 May 2015: Updated link to one of the downloads.