Tag Archive for Team Foundation Server

Team Foundation Server 2010 – Observations on Migrating

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!

Moving to Team Foundation Server 2010

I love it when a new wave of releases comes out from Microsoft. Sure, there’s more to learn and absorb, but more importantly it’s time to apply planning and installation exercises with new technologies. When it comes to planning solution architecture, you have to keep testing your methodologies – “Does our approach to planning for MOSS 2007 work as well for SharePoint 2010?” for example. I enjoy this exercise.

The technology team here recognized on Monday that now was the time to move our client projects to the new platforms – run our tests, address compatibility issues, etc. My tasks were focused on planning and performing the migration of Dynamics CRM and Team Foundation Server solutions to a new lab environment. The CRM was not really a platform migration; we simply decided that it needed a new home. However, we are all anxious to start leveraging the latest and greatest with TFS.

For those who are still using Visual SourceSafe, I’m truly sorry. The good news is that now is your chance to make the move to TFS (i.e. convince your program manager that it’s time to make the move). I saw this announcement at a Microsoft partner event last fall and still cannot believe the price point on TFS 2010. Essentially, if you have an MSDN license, you’ve got TFS: http://blogs.msdn.com/buckh/archive/2009/10/20/tfs-2010-server-licensing-it-s-included-in-msdn-subscriptions.aspx

Next Question: does TFS 2010 support the new technologies we want to use: Windows Server 2008 R2, SQL Server 2008 R2 and SharePoint Server 2010? Yes, Yes, and Yes. AS you can see from this excellent blog, the setup and administration capabilities have been vastly improved. I remember conversations with TFS 2005/2008 architects wherein they outlined the pain involved in getting all of the components to play nicely together. In 2010, the setup operations have been separated from the install – very similar to the approach taken with SharePoint ( and SSRS before it) – the result is a set of optional features which can be turned on after you have confirmed that more important features are working (like say, project collections and builds) http://blogs.msdn.com/bharry/archive/2009/04/30/tfs-2010-admin-operations-setup-improvements.aspx

Here are the critical downloads for getting your team up and running with TFS 2010:

Team Foundation Installation Guide for Visual Studio 2010

Administration Guide for Microsoft Visual Studio 2010 Team Foundation Server

I found this Upgrade Guide also very, very useful: