Important: The instructions in this post only apply to the RC version of Team Foundation Server 2010. For TFS 2010 Beta2, see this post. For TFS 2010 Beta1, see this post.
When you upgrade your existing Team Foundation Server to version 2010, upgraded team projects will work as before. However, you need to make some changes to these team projects if you want to enable the following features:
In this post, I’m providing a sample script to help you with many of the steps. For complete information about enabling these features, see the following article. Although it’s for Beta2, it is still applicable for RC:
Refer to the table below for a summary of the required changes to enable the new features for upgraded team projects. Note that these changes are only necessary for the team projects that existed before the upgrade. If you are creating new team projects, all of these features are enabled by default.
(*): You can use the sample script attached to this article to make these changes marked with (*) in the table above.
However, this sample script is designed to work if the following are true:
You need to either modify the sample script, or create your own if:
The attached ZIP file contains the script and updated MSF for Agile 4.2 work item type definitions. You must be a project collection administrator to run this script. The script requires the witadmin.exe utility which is installed by Team Explorer and Team Foundation Server.
To use the script, download and extract it to a local directory such as C:\Upgrade. Before you run the script, open “EnableFeatures.bat” in a text editor and complete the configuration by specifying values for the following:
Important: This script will only work against “unmodified” team projects created with “MSF for Agile Software Development – v4.2” process templates on RC version of Team Foundation Server 2010.
The script is a simple batch file that uses the witadmin.exe utility to make the following changes:
If you have any questions about the script, feel free to contact me.