Azure DevOps Blog
DevOps, Git, and Agile updates from the team building Azure DevOps
Latest posts
Load Test Enhancements in Release Candidate of Visual Studio 2015 Enterprise edition
What an amazing day. Today we announced the release candidate to Visual Studio 2015..and it has a ton of new features. If you haven’t already seen the news make sure and check out the following resources: In addition to downloading Visual Studio 2015 Release Candidate (RC), .NET Framework 4.6, Team Foundation Server 2015 RC, and Visual Studio 2013 Update 5 RC you can also use an Azure VM image to try out these releases. I am just wrapping the last of the RC publishing and realized I hadn’t done a post on my teams features-Load Test. Since November 2012 Cloud based Load Testing has released an amazi...
Code maps now differentiate test projects, and bring code context into map elements
Today Soma announced the Release Candidate of Visual Studio 2015. It adds two useful improvements to the Code Maps feature, which can make it easier to create better designs and architectures for your applications. The first improvement is in the way that code maps display and interpret test assets within solutions. The second improvement is in the way that the context of your code is carried through into the elements on the map. Test project differentiation In Visual Studio 2103, test assets (such as test projects and classes) are displayed in exactly the same way as other types of code items. For example, ...
What’s new in CodeLens for Visual Studio 2015 RC?
On April 17, 2015, we announced the General Availability of CodeLens in Visual Studio Online. However, the biggest news by far is that, in addition to Visual Studio Enterprise, CodeLens is now available in Visual Studio Professional 2015. This is one of the top requests we’ve had from customers. It received 3,461 votes on user voice. We have now marked this feedback item as “Completed”. CodeLens indicators for all types of files In Visual Studio 2015 CTP6, we added CodeLens file-level indicators for C++, JavaScript & SQL files. File-level indicators appear once for each file, at the bottom of the editor ...
Visual Studio Emulator for Android in VS2015 RC
Since our initial launch of the Visual Studio Emulator for Android, we’ve worked quickly to deliver on top feature requests, adding in support for hot-ticket items such as OpenGL ES 2.0, Lollipop, multi-touch, and advanced camera simulation. Today we’re announcing two more features to help you debug and test your Android apps on our fast, Hyper-V compatible, x86 emulator: Device Profiles and WiFi simulation. Device Profiles It’s no secret that testing your Android app for compatibility across the staggering variety of Android hardware can be a challenge. Android phones and tablets in the marke...
Walkthrough of Live Debugging using IntelliTrace in Visual Studio 2015 (Social Club)
In this blog post I am going to walk you through fixing a bug using IntelliTrace in Visual Studio 2015. If you haven’t done so already, check out the announcement of IntelliTrace in Visual Studio 2015 which gives you an overview of IntelliTrace and its UI. You can see this walkthrough as a video here (demo start at 1m30s). The application we are going to be working with is a WinForms application from CodeProject called SocialClub. The application lets you maintain a database of members for a social club. The bug I want to fix is that search behaves erratically after a member is registered. To reproduce the...
Diagnosing Event Handler Leaks with the Memory Usage Tool in Visual Studio 2015
Memory Usage tool in the Diagnostics Tool window In Visual Studio 2015 CTP 6 we introduced the new debugger-integrated diagnostics tools, including the Memory Usage tool. For the first time, you could investigate memory growth on the managed heap without leaving everyone’s favorite tool, the debugger. Based on your feedback, we’ve been refining the experience for Visual Studio 2015 RC. In this blog post, I’ll demonstrate how to use the Memory Usage tool while debugging to find and fix a common source of leaks in .NET code: event handlers. Along the way, I’ll introduce the updated UI. The sample app For this wa...
Continued Improvements for Breakpoint Configuration in Visual Studio 2015
By now you have hopefully heard that in Visual Studio 2015 we are introducing a new Breakpoint configuration experience. It features a Breakpoint Settings peek window that allows you to easily configure Conditions and Actions for a breakpoint by specifying a Conditional Expression, a Hit Count, a Filter, or by creating a Tracepoint. All of the links above point to blog posts that I have updated to capture the latest experience for breakpoints, and they also provide detailed examples of how to set and use configured breakpoints, so I recommend that you read them too. In this post, I will summarize only the changes...
.NET EnC support for Lambdas and other improvements in Visual Studio 2015
Hopefully you saw our previous post covering newly supported edit types added in our previous CTP of Visual Studio 2015 (if not, I’d recommend looking at that post first). Now, we are pleased to announce that Visual Studio 2015 RC contains even further Edit and Continue (Enc) improvements when debugging .NET applications. New Edit and Continue functionality Visual Studio 2015 RC adds the ability to: Note: Edit and Continue does not work for ASP.NET 5 applications at this point in Visual Studio 2015, but it is something we are working on and will ship as soon as it’s ready. A few notes ...
C++ EnC in Visual Studio 2015
One of the most useful features of the Visual Studio debugger is Edit and Continue (EnC), which works for both managed and native code (where native admittedly had some significant limitations in previous versions of Visual Studio through 2013). In this post I want to share some changes to EnC for C++ developers with Visual Studio RC, and also share our plans for VS2015 RTM. First let’s look at the C++ EnC against x86-built targets, and then we’ll look at 64 bit. C++ EnC x86 In Visual Studio 2013 you had to explicitly turn on edit and continue for native code because enabling it causes the debugger to fall bac...