Azure DevOps Blog

DevOps, Git, and Agile updates from the team building Azure DevOps

Team Foundation Server Extensions

Extensions enable publishers (partners, customers, developers) to create first-class, integrated experiences within Visual Studio Team Services. They enable integration at the UI layer – surfacing the relevant information in the right places and streamlining the user experience. An Extension can be a simple context menu, toolbar action or ...

Using the New Exception Helper in Visual Studio 2017

Dealing with exceptions is a common developer problem no matter your technology or level of expertise. It can be a frustrating experience figuring out why exceptions are causing problems in your code. When you are debugging an exception in Visual Studio, we want to lessen that frustration by providing you with relevant exception information to...

Break on Exceptions Thrown only from Specific Modules in Visual Studio 2017

In Visual Studio 2015 we introduced the new Exception Settings window which provides you a quick way to configure the debugger to break when exceptions are thrown. As part of that window revamp, we heard that simply filtering by exception type is not always good enough, you need finer grained control over when the debugger breaks on thrown ...

Release Management in TFS 2015 Update 2

With the release of Team Foundation Server 2015 Update 2 at //Build 2016, you get all the new Release Management (RM) features integrated right into TFS. The Release hub in the TFS web interface is your entry point to managing and tracking all of your application deployments. Here is a quick run through of the various features in Release...

What’s new in Git for Windows 2.8?

Download Git for Windows from its home page. Authentication is now a breeze More and more Git hosting sites support multi-factor authentication or security tokens. With the inclusion of the Git Credential Manager, Git for Windows now offers a user-friendly way to support such authentication methods. Git for Windows closely follows Git ...

Executing Automated tests in Build vNext using Test Plan, Test Suites

With Sprint 97 deployment on VSTS, users who have invested in planned testing using Test Plan, Test Suites can trigger automated runs in Build vNext. This functionality has been added to the Run Functional Tests task (formerly called Run Tests using Test Agent) as shown below. This functionality is also shipping in Team Foundation Server ...

New Build 2016 Partner Extensions in the Visual Studio Team Services Marketplace

Today at Build 2016, we featured two new extensions from our Partners that are now live in the Visual Studio Team Services Marketplace. It’s been fantastic to see the growth of the extensions since we introduced the Marketplace at Connect(); // 2015 a few months ago.  If you didn’t catch the live session today, we’ll have the recording ...

Updates for Debugging Installed App Packages in Visual Studio 2015 Update 2

In Visual Studio 2015 Update 2, we added support to the Debug Installed App Package dialog for: Starting an installed application on Xbox, HoloLens, and IoT (Internet of Things) devices Attaching to processes already running on IoT devices Sorting the apps based on "Running" or "Not Running" state Note that attach to process is...

Visual Studio Team Services announces the newest release of our Eclipse Plugin: Team Explorer Everywhere (TEE) 14.0.3

We are pleased to announce the availability of Team Explorer Everywhere 14.0.3, our Visual Studio Team Services and Team Foundation Server plug-in for Eclipse. Download locations: The command line client, SDK, and Eclipse plugin are all available for download here. The Eclipse update site is available here: http://dl.microsoft.com/eclipse...

Implement Rollback with Release Management for TFS 2015

When a deployment fails, it is likely to leave an environment in an unhealthy state. A rollback strategy is required to get the environment back to a healthy state. There are various options that can be considered as a rollback strategy. Option#1 : Undo the change by redeploying the previous release The first option is to simply ...