Azure DevOps Blog
DevOps, Git, and Agile updates from the team building Azure DevOps
Latest posts
JavaScript/Native Interop Debugging in Visual Studio 2013
Hello, I am Patrick Nelson, a developer on the Visual Studio Debugger Team. Authoring apps that are using more than one language is not uncommon these days. For example, some developers prefer one language for the UI layer but use another language (or reuse components in another language) for their business logic. When debugging such apps, most of the time you are either debugging one language or the other (and you select which debugger type you want to use through the project properties), but sometimes you need to have the debugger attached to both. In other words, you want to be using both debugger engines at ...
Seeing function return values in the Visual Studio 2013 debugger
You asked, and we have listened. Seeing return values for functions is something that many .NET developers wanted, and voted heavily for on the Visual Studio uservoice site. This feature exists already for C++ code and the good news is that with the latest version of Visual Studio, it’s here and you’ll be able to use it for your .NET code too. This new feature allows you to examine the return value of a function when the developer steps over or out of a function during your debugging session. This is especially useful when the returned value is not stored in a local variable. Consider the following nested functi...
Visual Studio 2013 Preview: Git version control and Team Foundation Build
I'm here today (and trying real hard to not be jealous of those of you reading this from beautiful San Francisco) to share some new information about version control and Team Foundation Build (TFBuild) in Visual Studio 2013 Preview. Version control I doubt many of you are surprised to hear that one of our big investments for this release is Git. Git built in to Visual Studio and TFS Since January we've offered Git as a Visual Studio 2012 extension and on Team Foundation Service. Beginning today: <!-- Are you ready to get started, develop your app, and collaborate in Git? Visit our n...
Load testing with Team Foundation Service – Launching Preview and Early Adoption Program
As announced with Visual Studio 2013 launch, cloud based load testing with Visual studio Online is in Commercial Preview. This is open to all Visual Studio Online users. You can read more about it here.Getting Started links Usage limits and Early Adoption ProgramAll users of Team Foundation Service will be able to run load tests on the cloud starting today. This capability is free for now, and we have a limit of 15,000 virtual user minutes per Team Foundation Service account per month during the Preview period. Ex: If your load test consists of 250 concurrent virtual users, you will be able to ru...
Using Coded UI to test XAML-based Windows Store apps
In the last few months since Windows 8 RTM’ed, we have seen the number of apps on the Windows Store grow significantly. There are several different aspects to shipping a great app to the Store. One of these is testing your app to ensure that the bugs are flushed out and you have automated tests in place to ensure that you can make regression free enhancements to your app. Visual Studio 2012 enabled Manual testing and Unit testing for Store apps. In the subsequent updates, we continued to enhance these features. Several customers were asking when Coded UI tests could be used for UI testing the Store apps and I am...
Using Visual Studio 2013 to Diagnose .NET Memory Issues in Production
Update: Note this post has been updated for Visual Studio 2013 RTM and is the first of a two-part series. In the screenshots and examples Just My Code and Collapse Small Objects are disabled as covered in part 2. It is recommended that you read this post before reading part 2. One of the issues that frequently affects .NET applications running in production environments is problems with their memory use which can impact both the application and potentially the entire machine. To help with this, we’ve introduced a feature in Visual Studio 2013 to help you understand the .NET memory use of your applications from...
Why does Visual Studio 2013 display “Visual Studio 2010” in the Test settings dialog
Had a question come up today on one of the distribution lists: Why does the Data and Diagnostics adapter reference Visual Studio 2010 even in Visual Studio 2013? Turns out this dialogue is trying to convey that this is the old way or the “Visual Studio 2010” way of static code coverage where users need to configure individual assemblies for collection. In Visual Studio 2013 to get code coverage results you can just right click from the Test explorer I have also had people ask: How the heck do you get the Test Settings dialog to display!? The easiest way is to add one of t...
Part 3: Unit testing with Traits and code coverage in Visual Studio 2012 using the TFS Build – and the new NuGet adapter approach
The Unit Testing series by one of the ALM MVPs Terje Sandstrom has been some of the highest read posts on the ALM blog…In this post he shows how to easily provide unit Test Adapters from NuGet. Thanks for the Great Post Terje! ********************************************************** This is the 3rd post in a series on Unit Testing in Visual Studio 2012, this one focusing on how to use the new features with the TFS Build system, but also some news on unit testing in Visual Studio itself, in particular the use of NuGet as an engine for providing the adapters. We will also cover the setup and cus...
Microsoft Test Manager: Customization of test result fields and marking test results as NA
As part of the MTM enhancements in the Visual Studio Update 2, we introduced a feature to customize the test result analysis fields like 'Resolution' and 'Failure type'. Different projects may have different reporting needs and this feature lets you do just that. You can customize the values that appear in these fields based on your project requirements, using a simple command. This nice post by Colin Dembovsky talks in detail about this capability. We also introduced a new test outcome state called 'Not applicable' for marking test results in MTM or the TEST hub. When you are doing your test...