Uncategorised

All has been going well since our upgrade from TFS 2012 to 2013, no nasty surprises. As I had a bit of time I thought it a good idea to start the updates of our build and lab/test systems. We had only upgraded our TFS 2012.3 server to 2013. We had not touched our build system (one 2012 controller and 7 agents on various VMs) and our Lab Management/test controller. Our plan, after a bit of thought, was to so a slow migration putting in new 2013 generation build and test controllers in addition to our 2012 ones....

We are testing the ‘social publish’ plugin for BlogEngine. Rik’s post has the details on what needs to be done to get it working with the current Twitter APIs

Update 27 Jun 2013 See update version of post with more data I seem to be involved with a number of TFS 2010 to 2013 upgrades at present. I suppose people are looking at TFS 2013 in the same way as they have historically looked at the first service pack for a product i.e: the time to upgrade when most of the main issues are addressed. That said TFS 2013 is not TFS 2012 SP1!...

We have eventually got around to the 2013 upgrade of our production TFS server. It had been put off due to some tight delivery deadlines around Christmas. The upgrade went fine, unlike out some previous ones we have had. The upgrading of our team process templates, to add the new features, was greatly eased by using Feature4Tfs tool on CodePlex. This meant one command line call and all the projects were done (we had no significant process customisation) as opposed to visiting in team project in the admin console....

I am upgrade an internal system from .NET 4.0 to 4.5 so that I can use the Team API features in TFS. The system is based around a WCF web service that links our customer help desk system to TFS to keep bug reports in sync. It uses Entity Framework to access our help desk SQL DB. When I changed the targeted .NET framework for the WCF project, I started to get warning to update the Nuget managed references for EF, which I did....