As I mentioned in a previous post, we’re moving wholesale to the Wave 14 product set here at Blum Shapiro. I was back in the office today, moving our TFS installation to 2010 after a few days of planning last week and some client work yesterday. I wanted to share some observations.
First, many of the posts out there indicate that running the upgrade wizard is preferable starting with a clean install. The rationale is that it is difficult to get the content moved from SharePoint Project Team Sites if you start from scratch. The same issue exists for Reporting Services integration.
I agree with this approach because not everyone is fluent in SharePoint, Reporting Services and TFS/ALM concepts; it seems a terribly onerous requirement in order to find someone to get you to TFS 2010. However, internally we have not taken advantage of SharePoint work item tracking in TFS 2008, nor did we leverage the analysis capabilities; we are a Solution Architecture, SharePoint and BI consulting firm, not an ISV. Therefore, my objectives were a bit simpler – move the source code with as little disruption as possible.
To move the source code with as little disruption as possible, I suggest creating a fresh TFS 2010 install and then importing the TFS 2008 projects into their own project collection. I found this blog post helpful in importing the old TFS 2008 projects: http://blogs.msdn.com/b/bharry/archive/2009/10/21/upgrading-from-tfs-2005-2008-to-tfs-2010.aspx
Two things it does not mention are:
1. The TFS 2008 databases need to be SQL Server 2008 databases
2. Keep the database names intact (i.e. TfsBuild, TfsIntegration, TfsVersionControl, TfsWorkItemTrackingAttachments, TfsWorkItemTracking, TfsWarehouse)
Upon realizing that I needed to “upgrade” my databases from 2005 to 2008 before I could upgrade, I decided to get cute and rename the databases with TFS2008 in the name. Getting cute never pays off.
Also, in order to eliminate any risk of mixing and matching process templates from TFS 2008 into TFS 2010, I created a dedicated project collection for new TFS 2010 projects.
Finally, any of your colleagues who are still in transition from Visual Studio 2008 will need to follow these instructions: http://blogs.technet.com/b/chrad/archive/2010/01/08/visual-studio-2008-connecting-to-tfs-2010-server.aspx
I’m looking forward to playing with the new Build Server in TFS 2010! Enjoy!