Hakan Eskici : TFSUpgrade

Team Foundation Server 2010 Beta 2 Available

Hakan Eskici — Thu, 22 Oct 2009 13:16:14 GMT

We have just announced the availability of Team Foundation Server 2010 Beta 2 along with the Ultimate, Premium and Professional editions of Visual Studio 2010.

Download Links:

Related Resources

Where is Web Access?

Web Access is integrated into Team Foundation Server and gets installed by default when you install Team Foundation Server.

On a default configuration, Web Access is available at:

http://server:8080/tfs/web

Where is Work Item Only View (previously known as WIWA)?

WIOV now shares the same URL with full Web Access:

http://server:8080/tfs/web

There is a new permission to control access to full Web Access features. Anyone in the “Work Item Only View Users” group will have that permission denied, therefore they will see the Work Item Only View. Others will see full Web Access.

How can I install Web Access separately on its own server?

The recommended way is to install a “Application Tier Only” instance of TFS by pointing it to the same TFS database and using that instance just for Web Access. For example:

Server1: End users connect to this server from Team Explorer (Web Access is available but not used)
Server2: Web Access users connect to this server from a Web browser (TFS Application Tier is available but not used)

Sample Script to Enable New Features in Upgraded Team Projects (TFS 2010 Beta2)

Hakan Eskici — Mon, 19 Oct 2009 20:40:00 GMT

Important: The instructions in this post only apply to the Beta2 version of Team Foundation Server 2010. For Beta1, see this post.

Introduction

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:

Test Case Management
Agile Planning Workbooks
Lab Management

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:

Enabling New Application Lifecycle Management Features for Visual Studio Team System 2010 Beta 2 in Upgraded Team Projects

Required Changes

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.

Feature	Requirements
Test Case Management	Add Test Case and Shared Step work item types () Update existing Bug and Scenario work item types () Add new link types () Add work item categories ()
Agile Planning Workbooks	Update existing Task and Scenario work item types (*) Create iteration and product backlog queries Bind workbooks against the queries Modify workbook document properties
Lab Management	Grant lab management permissions to user groups Provision lab resources
Reports	Update your existing reports to work against the new warehouse

(*): 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 are using the Beta2 (English) version of Team Foundation Server 2010
Your team project was created with the English language version of “MSF for Agile Software Development - v4.2” process template before you upgraded your Team Foundation Server
No modifications have been made to the work item type definitions on your team project before or after the upgrade
You are running the script on an English operating system that has Visual Studio Team Explorer 2010 Beta2

You need to either modify the sample script, or create your own if:

Your team project was created with a process template other than “MSF for Agile Software Development v4.2” (English)
You have made modifications to the out of box work item type definitions on your team project
Your team project already has an existing Test Case work item type
You want to use the existing “Repro Steps” field on your Bug work item type
You are using a non-English Team Foundation Server

Sample Script

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:

Team Foundation Server URL
Name of the team project collection
Name of the team project
Path to witadmin.exe utility
Set ConfigComplete = 1 to indicate that you’ve completed the configuration

Important: This script will only work against “unmodified” team projects created with “MSF for Agile Software Development – v4.2” process templates on Beta2 version of Team Foundation Server 2010.

What does the script do?

The script is a simple batch file that uses the witadmin.exe utility to make the following changes:

Saves a backup of your existing Bug, Task and Scenario work item types
Adds new link types (Test Case / Shared Steps and Tests / Tested By)
Adds new work item types (Test Case and Shared Step)
Overwrites Bug, Task and Scenario work item types
Adds work item categories

Download the Sample Script

If you have any questions about the script, feel free to contact me.

Enable Branch Visualization in Upgraded Team Projects (TFS 2010 Beta1)

Hakan Eskici — Tue, 19 May 2009 23:29:51 GMT

As part of the series on “enabling new features in upgraded team projects”; Jamie Cool, our Lead Program Manager on Team Foundation Server team, talks about enabling branch visualization features in upgraded team projects:

In Team Foundation Server 2010, we have significantly enhanced the concept of a branch. We have added functionality to branches such as:

Branches can now be clearly identified in the source control explorer.

You can now visualize your branch hierarchy and visually track your code changes as they move through your branches.

You can assign branch operation security. Ex. Who can create/delete a branch and who can merge a branch.

Branches now have checks in place to discourage poor branching structures.

In order to take advantage of these new features, you will need to convert your previously branched folders to fully fledged branches. The steps for doing this are as follows:

Identify the branch structure you are currently using. If you would like to change your branch structure, now may be a good time to do so, but it is not necessary.

Identify the folder in your solution explorer mapped to your parent (top level) branch.

Right click on that folder. On the context menu select “Branching and Merging” & then “Convert Folder to Branch”. This will open a dialog for doing the conversion of a folder to a branch.

At the bottom of the dialog, check the “Recursively perform this conversion for all branched child folders”.

Next click the “Convert” button. This will upgrade this folder to a branch. It will also walk the branch tree and convert all folders that have been branched from this folder.

Your branches should now be shown with the branch icon in the source control explorer tree.

If you have any folders that had their relationship established via Baseless Merge, you will need to use the “Reparent Branch” option from the “Branching & Merging” context menu to establish the parent/child relationship in the branch hierarchy.

Repeat these steps for all remaining branch trees in your solution.

Now that you have completed this step, you should be able to take advantage of the powerful new branching features in Team Foundation Server 2010. You can now view your branch structure visually by selecting “Branching and Merging” and then “View Hierarchy” from the branch context menu. You can also choose to “Track Changes” from a work item’s context menu to see how the changeset associated with that work item has moved through your various branches.

You can check out the MSDN documentation on Branch Visualization to learn more about the capabilities available to you:

How to: View the Branch Hierarchy of a Team Project

How to: View Where and When Changesets Have Been Merged

Enjoy!

Jamie Cool