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.
By now, hopefully you’ve heard about the new Visual Studio Emulator for Android, which is available as a standalone download for Eclipse and Android Studio users. Today, we’re issuing an update that addresses some of your top requests, including network simulation and improved screenshot functionality.
[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,
The Concurrency Visualizer is a tool for Visual Studio that allows you to analyze and improve performance of multi-threaded Windows Desktop applications. See the MSDN documentation for more information on using the Concurrency Visualizer.
The Concurrency Visualizer was included with Visual Studio 2010 and Visual Studio 2012,
Poor performance is one of the largest causes of lost business on the Internet. Companies are increasingly more concerned with losing business (like during the upcoming Holiday season) due to insufficient capacity sale and most/all development teams want to measure their applications performance BEFORE it hits production.
Last week I was asked a pretty common question:
“How do you generate and distribute load in a Performance Test across different geographic locations”
This person knows our load Testing features well and knew about the new location picker (see below).
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,
Today, a few short weeks after our initial release of the work item reporting capabilities in the Visual Studio Online Power BI Connector, we are happy to announce the general availability of trend and rollup reporting capabilities. Starting today you can do things like create sprint burndown charts based on story points,
Tests broadly classified as integration tests or functional tests are often in need to connect to external app resource (web application, API front end, or a DB tier) to drive validations. Maintaining lifecycle of such tests from the environment where it’s authored (dev machine with VS) to all the other places where they might be consumed (as part of Build/CI Tests,
Yesterday, we released the Visual Studio 2015 version of the CodeLens Indicator for Code Health in Visual Studio Gallery. This extension is an update to the Visual Studio 2013 version, which we had released in Sep 2013 as a Microsoft DevLabs extension.