Having installed my TFS Alert DSL today onto a client’s TFS 2013.2, I have realised some of the documentation was a little unclear. So I have have just updated the download page to provide an easy means to get The actual DSL implementation (without rebuilding the source) A command line tool to create an event source in …

The problem Today I found I had a problem when trying to associate a Release Management 2013.2 release pipeline with a TFS build. When I tried to select a team project the drop down for the release properties was empty. The strange thing was this installation of Release Management has been working OK last week. What …

I have just submitted a session for DDDNorth 2014, which is at the University of Leeds on Saturday 18 October. There is still time for you to submit yours Session submission

Rik recently posted about the work we have done to automatically provision TFS build agent VMs. This has come out of us having about 10 build agents on our TFS server all doing different jobs, with different SDKs etc. When we needed to increase capacity for a given build type we had a problems, could another agent run …

I am currently rebuilding our TFS build infrastructure, we have too many build agents that are just too different, they don’t need to be. So I am looking at a standard set of features on a build agent and the ability to auto provision new instances to make scaling easier. More on this in a future post… Anyway whilst …

Whilst working on an automated build where I needed to target a specific project I hit a problem. I would normally expect the MSBuild argument to be /t:MyProject:Build Where I want to build the project Myproject in my solution and perform the Build target (which is probably the default anyway). However, my project was …

If you are doing any work with Azure Cloud Applications there is a very good chance you will want your automated build process to produce the .CSPKG deployment file, you might even want it to do the deployment too. On our TFS build system, it turns out this is not a straight forward as you might hope. The problem is …

All teams have ‘Stakeholder’, the people the are driving a project forward, who want the new system to be able to do their job; but are often not directly involved in the production/testing of the system. In the past this has been an awkward group to provide TFS access for. If they want to see any detail of the project …

My Channel9 Guy has a new MVP badge

Nice post by Riccardo Viglianisi, one of Black Marble’s Testers, about his experiences with CodeUI and Windows Store Apps published on the MSDN UK Visual Studio blog. Well worth a read if you are looking at this technology.