A hotfix package is available for Visual Studio 2010 Team Foundation Server Beta 2 that resolves several configuration problems

Article translations Article translations
Article ID: 977226
Beta Information
This article discusses a beta release of a Microsoft product. The information in this article is provided as-is and is subject to change without notice.

No formal product support is available from Microsoft for this beta product. For information about how to obtain support for a beta release, see the documentation that is included with the beta product files, or check the Web location where you downloaded the release.

This article applies to Microsoft Visual Studio 2010 Team Foundation Server (TFS) Beta 2.
Expand all | Collapse all

On This Page


A hotfix package is available for Microsoft Visual Studio 2010 Team Foundation Server (TFS) Beta 2.

Note The hotfix should be installed after the configuration phase of the installation process.

The following configuration problems are resolved in this hotfix.

Problem 1

Work item tracking (WIT) data intermittently cannot be saved to the TFS 2010 warehouse.

Problem 2

The iteration backlog for each workbook is based on the root iteration and not on individual iterations.

Problem 3

When Decimal symbol is not defined as PERIOD (.) in the Regional and Language Options item in Control Panel, unexpected issues occur. For example, you define Decimal symbol as COMMA (,), and then you open a TFS 2010 project to manage tasks in Microsoft Office Project. In the project, a resource file name contains a comma. In this example, you find that the resource name is split unexpectedly.

Problem 4

Multiple work items cannot be saved in Microsoft Office Project or in Microsoft Office Excel when you use a TFS 2008 client to connect to a TFS 2010 server.

Problem 5

After you perform a buddy build, the status of some files indicates that the files were checked out by the build server account.

Note To resolve problem 5, apply the additional steps that are described in the "More information" section after you install the hotfix.


Hotfix information

To obtain this hotfix package, visit one of the following Microsoft Web sites:

The TFS 2010 hotfix package from Microsoft Connect

The TFS 2010 hotfix package from MSDN Code Gallery


You must have Visual Studio 2010 TFS Beta 2 installed to apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform

Note If you still encounter these configuration issues after you apply the hotfix, send an e-mail message to tfsb2sub@microsoft.com with detailed information about the issue that you are experiencing.

Additional steps for problem 5

To resolve problem 5, change the process template files that the user can edit. To do this, follow these steps after you install the hotfix:
  1. Find the following template file:
    drive:\Program Files\Microsoft Team Foundation Server 2010\Tools\Deploy\ProcessTemplateManagerFiles\MsfAgile\Template_new.zip
    Rename the file to replace the following template file:
    drive:\Program Files\Microsoft Team Foundation Server 2010\Tools\Deploy\ProcessTemplateManagerFiles\MsfAgile\Template.zip
  2. Find the following template file:
    drive:\Program Files\Microsoft Team Foundation Server 2010\Tools\Deploy\ProcessTemplateManagerFiles\MsfFormal\Template_new.zip
    Rename the file to replace the following template file:
    drive:\Program Files\Microsoft Team Foundation Server 2010\Tools\Deploy\ProcessTemplateManagerFiles\MsfFormal\Template.zip
  3. Uncompress the template files from step 1 and step 2.

    Note Do not delete the original compressed (.zip) files.
  4. For each existing team project collection in TFS 2010, upload the new process templates from the template files.
  5. For each existing team project, replace the following Build Process Template files in version control with the new Build Process Template files:
    • DefaultTemplate.xaml
    • UpgradeTemplate.xaml

Known issue

The default process templates are not stored on the server. Therefore, you must upload the new process templates every time that you create a new team project collection.

Note This issue will be resolved in the release version of TFS 2010.


For more information about the details of problem 5, visit the following Microsoft Developer Network (MSDN) Web site:
Second TFS 2010 Beta 2 software update available

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates


Article ID: 977226 - Last Review: October 7, 2011 - Revision: 2.0
kbexpertiseadvanced kbfix kbsurveynew kbqfe KB977226

Give Feedback


Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com