Skip to main content

Adding a build agent to TFS 2015

I was shocked how simple we can create and attach a new build agent to TFS 2015. There are only a few simple and small steps that we need to do.
The new build system that comes with TFS 2015 and Visual Studio Team Services (Visual Studio Online) is not using anymore the old and classic XAML build definition. The new one allows you to define the build as a flow of events where you can specify at each step what do you want to happen. This is done easily  directly from the web portal.

If you need to create or add a new build agent to your TFS 2015 infrastructure, than you will be shocked how easily this can be done.
First step is to download from the "Agent Pools" tab the agent.
Once you done this step, you will need to run the executable on the machine that will become the new Build Agent. I recommend to run the executable file from a command prompt and provide all the information that are required. You only need to know the TFS 2015 address and to have access to TFS as "Agent Pool Service Account".
And we are done!

You will find out that you cannot run the build directly. This will happen because you will need to install the application that are needed by your build (msbuild, visualstudio, vstest). The error that is displayed when you didn't install all that you need looks like the one below.
"No agent found in pool 1 which satisfies the specified demands"

Don't worry. The installation of all this dependencies is smooth and you don't need to do any kind of custom confirmation.

A good MSDN starting point:


Popular posts from this blog

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…

GET call of REST API that contains '/'-slash character in the value of a parameter

Let’s assume that we have the following scenario: I have a public HTTP endpoint and I need to post some content using GET command. One of the parameters contains special characters like “\” and “/”. If the endpoint is an ApiController than you may have problems if you encode the parameter using the http encoder.
using (var httpClient = new HttpClient()) { httpClient.BaseAddress = baseUrl; Task<HttpResponseMessage> response = httpClient.GetAsync(string.Format("api/foo/{0}", "qwert/qwerqwer"))); response.Wait(); response.Result.EnsureSuccessStatusCode(); } One possible solution would be to encode the query parameter using UrlTokenEncode method of HttpServerUtility class and GetBytes method ofUTF8. In this way you would get the array of bytes of the parameter and encode them as a url token.
The following code show to you how you could write the encode and decode methods.