Work around now commercial features of OpsHub VSO Migration Utility


OpsHub has a relatively simple tool to help you migrate your work items and version control data from an on-premise TFS server to Visual Studio Team Services. They recently released version 2.0, which brings a number of improvements.

Unfortunately this new version has also removed some of the features which were previously free and moved them to an intermediate commercial version between the Free and the full fledged OpsHub Integration Manager.

Mount OneDrive as a Network Drive


Ever wanted to upload a lot of data to OneDrive without having to sync that folder to your local machine (updating my music library is pretty hard, as to put data into the folder, I first need to sync it locally).

Ever wanted to download a few specific files from OneDrive without syncing them first?

Ever wanted to operate on your OneDrive files as if they were real local files?

That is all possible! The trick is to mount your OneDrive as a Network Drive. The trick is pretty simple and is explained here. The only thing I have to add to it is that if you're using 2-Factor Authentication (which you should), then you'll need to generate an app-specific password.

Visual Studio Online is now Visual Studio Team Services


In an attempt to remove the confusion whether Visual Studio Online is an IDE in the Cloud, Microsoft has decided to rename Visual Studio Online to:

Visual Studio Team Services

Which nicely abbreviates to VSTS, an acronym people who were using TFS in the 2005 and 2008 era may remember :). In remembrance of that great heritage:

Note to self: Here we go again, renaming all tags on the blog and trying to get the StackOverflow tag renamed *again*.

Debug your TFS/VSO 2015 builds

The new build engine of Visual Studio Online and TFS 2015 is great. It's simple, easy to configure and doesn't require complex workflow designers. But when it's not doing exactly what you want it to do, it can be hard to figure out where it's going wrong.

There is a trick to enable verbose logging on the tasks of your build, which will make them generate lot more information. This additional information has saved me more than once since I learned of the existence of this trick.

To enable debug logging simply create an extra build variable called System.Debug and set the value to true.

Enable parallel execution of tests using the Visual Studio Test Runner 2015.1


Does your machine have multiple CPU's or cores? Are your tests truly independent and thread safe? In that case you'll be able to speed up your test runs considerably by enabling multi-threaded support to the Visual Studio Test Runner.

This works in both Visual Studio as on your build server.

To get the benefits, add the following snippet to your .runsettings file:

<?xml version="1.0" encoding="utf-8"?>
    <!-- Add this line, default is 1, which makes it run single threaded -->
    <!-- 0 will use all available cores -->

This is an all or nothing setting in Visual Studio, but in TFS Build you can specify multiple test runs, each with their own .runsettings. So for your CI build you'll be able to run all your unit tests in parallel, but then execute your integration tests serially, if needed.

This setting is built into the test runner, as such it doesn't require special support from the test adapters for the different frameworks.


Most Reading