[Updated April 5th: In the "Plans for H1" section, added links to blog posts on released features] Back in September Stuart explained our SonarQube Integration plans with Visual Studio, TFS and Visual Studio Team Services. In December he updated the blog post with what we had done. With the Visual Studio Team Services Features Timeline being upda...

Last month we released the MSBuild tasks for SonarQube analysis, which make it easy to analyze a .NET project. Today we are pleased to announce an updated Maven task that makes it easy for Java developers using Maven to trigger a SonarQube analysis in Visual Studio Online (VSO), and - when Update 1 is available soon - in Team Foundation Server (TFS...

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 p...

_ 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 More succinct conso...

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, we have been working with SonarSource to integrate SonarQube with MSBuild, Team Foundation Ser...

[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 bet...

When you want to understand specific dependencies in your code, visualize them by creating code maps. You can then navigate these relationships by using the map, which appears next to your code. Code maps can also help you keep track of your place in the code while you work or debug code, so you'll read less code while you learn more about your cod...

Amongst the improvements we’ve made to Code Maps in Visual Studio Enterprise 2015 RTM are: The icons are now consistent with Solution Explorer and other tools The following screenshot shows a code map in Visual Studio 2015 RC. You can see that, although the nodes are decorated with icons, these are of varying sizes and some are not even sim...

Code Maps, previously known as Directed Graph Documents, are a great way to visualize the relationships and interdependencies between the components of your applications. They make it much easier to understand the architecture of your (or, even more useful, somebody else’s) application, and where you should start when you need to update the applica...

Code Maps, previously known as Directed Graph Documents, are a great way to visualize the relationships and interdependencies between the components of your applications. They make it much easier to understand the architecture of your (or, even more useful, somebody else’s) application, and where you should start when you need to update the applica...