Azure DevOps Blog
DevOps, Git, and Agile updates from the team building Azure DevOps
Latest posts
Driving Unit Tests from Cloud Load Test
** Visual Studio Load Testing has always made it easy to create Load Tests. Now with Visual Studio Online it is also easy to verify the performance capacity of your software of 1,000s of users external to your data centers using the Cloud and Microsoft Azure. It has been noted that Visual Studio Load Testing is widely used inside of Microsoft from its inception back in 2005; which begs the question since many of Microsoft development teams are NOT working on web pages, how are they using Visual Studio Load Test? Many (most?) Microsoft developers are writing services and since Visual Studio Load Test can also...
Deploying using PowerShell Desired State Configuration in Release Management
With Microsoft Release Management 2013 Update 3 RC, you can now use Windows PowerShell or Windows PowerShell Desired State Configuration (DSC) for deploying and managing configuration data. > Windows PowerShell (PS) > > Refer to Scripting with Windows PowerShell (PS) for more details. These scripts can be same as what you might have been already using to deploy using Microsoft Deployment Agent. > > RM 2013 Update 3 “Deploy using PowerShell” requires PS version on the target servers to be of version 4.0 or higher. > > Windows PowerShell Desired State Configur...
Where is the field on the work item form to order the backlog?
In our latest deployment to Visual Studio Online on July 1, we have removed the Stack Rank (Agile / CMMI) or Backlog Priority (Scrum) field from the work item form. The backlog uses that field to order the items and updates the field to arbitrary values, which caused confusion. If you are interested in the detailed background, please read a previous post called “Behind the scenes: the Backlog Priority or Stack Rank field”.When we introduced the field in TFS 2012, the intention was to make it a system field, hidden to the user. But for a variety of reasons, such as keyboard accessibility, we added it t...
Load Testing with Visual Studio Online
Check for performance issues on your web site before they impact your customers. Perhaps you expect an increased user load from a marketing campaign. Use cloud-based load testing with Visual Studio Online to test if your application can handle all the new users. With cloud-based load testing it’s easy: Watch a short video about load testing with Visual Studio Online Highlights a Latest feature addition: Load testing with Visual Studio Online integrates with Application Insights to get the application performance data during the load run. It's now much ...
How to trigger deployments to Chef managed environments from Release Management 2013 with Update 3 RC
Pre-requisites for triggering Chef deployments using RM: Deployment using Chef: · Server name should be same as node name registered with Chef Server. · Port should be same as registered with Chef Server. Use ssh port for Unix based systems and WinRM port for windows based systems. 4. Create vNext component and provide the path to package using Build externally option. It can be http/ftp path as well. Note: · &nbs...
Get Application Performance Counters of your choice during load runs with Visual Studio Online
Goal of a load testing activity is to identify and fix performance bottlenecks. Visual Studio Online integrates Cloud Load Testing with Application Insights to give deep insights into performance and diagnostics data of your application which dramatically decreases the discovery and resolution of any issues discovered later. This article will walk you through configuring Load Testing to take advantage of Application Insights. With the latest release of Visual Studio Update 3 RC, you will be able to monitor any of the performance counters during the load run. *Please note that Application Insights is in Preview. ...
How to deploy to Standard or Azure environments in Release Management 2013 with Update 3 RC
With Microsoft Release Management 2013 Update 3 RC, you can now use Windows PowerShell or Windows PowerShell Desired State Configuration (DSC) for deploying and managing configuration data. We now support deploying to On-premise environment (Standard) and Azure environments without having to setup Microsoft Deployment Agent. Prerequisites PowerShell (PS) You can use PS scripts to deploy application components to Standard or Azure servers. These scripts can be same as what you might have been already using to deploy to Microsoft Deployment Agent based servers. RM requires the PS ve...
How to setup environments for Agent-less deployments in Release Management 2013 with Update 3 RC
With Microsoft Release Management 2013 Update 3 RC, you can now use Windows PowerShell or Windows PowerShell Desired State Configuration (DSC) for deploying and managing configuration data. We now support deploying to On-premise environment (Standard) and Azure environments without having to setup Microsoft Deployment Agent. Prerequisites PowerShell (PS) You can use PS scripts to deploy application components to Standard or Azure servers. These scripts can be same as what you might have been already using to deploy to Microsoft Deployment Agent based servers. RM requires the PS versi...
CodeLens Processing pipeline performance improvements
Introduction CodeLens is a heads-up display in your Visual Studio Editor where you can find information about your code in-context. See this MSDN article for an introduction to CodeLens - Get history and other info about your code. In a previous blog post, I had described the CodeLens Team Indicators – Processing Pipeline. I recommend, you read that article before going further since I will be referring to the concepts introduced there. In this blog post, I will describe some of the performance optimizations we have done for various jobs in the CodeLens processing pipeline as part of Team Foundation Server 201...