Over a year ago I’ve posted a guide on how to upload a custom build task to Team Foundation Server 2015. The solution was based on a TFS REST api which allowed to manipulate build tasks easily. Things have changed since then unfortunately…

Over a year ago I’ve presented a solution to copy build definitions between team projects in new Team Foundation Server 2015. That was a workaround for missing functionality in TFS, so there was no standard way to save the build definition as a template and reuse it outside the scope of current team project. Well, in TFS 2017 it hasn’t change yet…

Recently we’ve installed and configured the Team Foundation Server on premise infrastructure. This was described here. In this post I would like to show you how to install and configure the build agent to work on a different machine separately from the TFS server, as it turned out to be quite tricky.

If you didn’t yet happen to create a custom build step for Team Foundation Server 2015 take a look at my previous posts here and here. Today I will show you the right (IMHO) way of calling MSBuild from the custom build step.

In previous post I showed you how to create a custom build step, upload and use it in the Team Foundation Server 2015. This time we will try to create more complex build task. This will be FTP uploader. Keep reading.

If you have a nuget packages that you deploy from your source code and want to move to the TFS 2015, there are good news. Packing and publishing nuget packages is fully supported in vNext build definition. Let’s see how to achieve that.

The new vNext build system in TFS 2015 is simpler and easier to manage than the previous version, Windows Workflow based, build system. It builds up from a collection of build step which you can add and remove. The collection of available build steps is pretty rich and can be extended by a custom build steps. In this post I will show you how to easy create and deploy a custom vNext build step.