Update 2013-09-12: I’ve updated the extension to work with VS 2013 RC (since there were some breaking changes from Preview).
One of my favourite reports in TFS is the Backlog Overview (Scrum) or User Story Overview (Agile). So after installing and playing with TFS 2013 Preview, I went to see what the report looks like.
Update 2012-09-04: Brian Keller posted a fix that seems to work for this problem (so you can run the InRelease build without connecting to a physical external network).
Are you (as a developer) inundated with frequent status updates? Requests like: “How far are you?” “What did you do today?” “Where are we?” Or are you a project manager that requests frequent status updates? Then this post is for you.
I’ve written about why builds are absolutely essential in modern application development (Part 1) and what why Team Build is a great build engine (Part 2). However, if you don’t include unit tests in your builds, it’s like brushing your teeth without toothpaste – there’s a lot of movement, but it’s not the most effective way to do things. In this post, I want to put forward a few thoughts about why you absolutely need to be unit testing.
Note: This post is NOT about TFS and Project Server integration – this is for adding, editing and deleting work items using MS Project.
Update 2013-08-30: The extension is now available for VS 2013.
In my previous post I wrote about why you should be doing automated builds in general terms. In this post I’ll show you how TFS’s automated build engine gives you consistency and quality in your build processes. There are other build engines, but if you’re using TFS for source control (and/or test management and/or lab management and/or work item tracking) then Team Build makes the most sense as a build engine since it ties so many other parts of the ALM spectrum together.