Azure DevOps Blog
DevOps, Git, and Agile updates from the team building Azure DevOps
Latest posts
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...
View Source in the CPU Usage tool
In Update 2 of Visual Studio 2013, we added the CPU Usage tool into the Performance and Diagnostics hub which allows you to see where the CPU is spending time executing your code. In Update 3 of Visual Studio 2013, we have made a small but important improvement to this tool: the ability to navigate from a function in the call tree to the source code where that function was defined. When you have found an interesting function to look at in the call tree, you can right-click on it and select “View Source” or select the line and press Ctrl+G: After you do that, the editor will open the corresponding source file ...
Application Insights tools for Visual Studio included in Visual Studio 2013 Update 3 RC
Today, as part of the Visual Studio 2013 Update 3 Release Candidate, projects enabled for Application Insights will result in an Application Insights resource being provisioned in an Azure subscription (visible in Portal Preview at https://portal.azure.com). Currently the Application Insights Blade shows “Coming soon…” - check back in mid-July for the actual blade. Before Visual Studio 2013 Update 3, projects enabled for Application Insights using the latest Application Insights tools for Visual Studio resulted in an Application Insights Application being created in a Visual Studio Online account. Note Appl...
CodeLens for Git improvements in Visual Studio 2013 Ultimate Update 3 RC
In Visual Studio 2013 Update 3 CTP1, we introduced some CodeLens for Git indicators. In this RC update we are completing the work by: CodeLens for Git indicators now react to Git source control operations In the CTP1, the authors and change indicators that we introduced did not refresh automatically when source control operations occurred. As a user, you had to manually refresh the indicators using the contextual command (or close and reopen the file) In this RC, all the CodeLens for Git team indicators now refresh automatically when you: The refresh occurs when performing these actions from Vi...