Introduction
A hotfix rollup (build number is 10.0.40219.359) is available for Microsoft Team Foundation Server (TFS) 2010 Service Pack 1 (SP1).
This hotfix rollup includes fixes for the following issues in TFS 2010 SP1.
Issue 1
When you run large build requests for a long time without restarting the TFS build service, the private working set of the TFS build service reaches more than 1 GB, and a memory leak occurs in the TFS build service.
Issue 2
When you use Microsoft Visual Studio to debug binaries and symbols from a TFS 2010 build, breakpoints that you set in the downloaded source files are ignored.
Issue 3
When you build a project in Visual Studio, the targets that are specified by the TargetsNotLogged property are still logged. Additionally, the build process takes a long time, and you receive the following information in the Build Details window:
Built <project> for default targets.
Built <dependent project> for target(s) GetTargetPath.
Built <dependent project> for target(s) GetNativeManifest.
Built <dependent project> for target(s) GetCopyToOutputDirectoryItems.
Note When this issue occurs, most of the build steps that are processed are unnecessary.
Cause
Cause of Issue 1
This issue occurs because the build tracking participant that is added to the extension of the workflow application is deleted incorrectly.
Cause of Issue 2
This issue occurs because the downloaded files do not have the same name as the original files.
More Information
The TargetsNotLogged property is used to reduce many "noise" entries in the log for the Team Foundation Build projects that contain project-to-project references. The TargetsNotLogged property is used to prevent the ProjectStartedEvents function from logging the specified targets. By default, the Microsoft.TeamFoundation.Build.Targets file initializes this property to ignore the following targets:
-
GetTargetPath
-
GetNativeManifest
-
GetCopyToOutputDirectoryItems
Resolution
To resolve these issues, apply this hotfix rollup on a bulid server that is running TFS 2010 SP1.
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that this article describes. Apply it only to systems that are experiencing this specific problem.
To resolve this problem, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft website:
http://support.microsoft.com/contactus/?ws=supportNote In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
Prerequisites
To apply this hotfix rollup, you must have TFS 2010 SP1 installed.
Restart requirement
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
File information
The global 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.
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Microsoft.teamfoundation.build.server.logger.dll |
10.0.40219.359 |
48,984 |
06-Nov-2011 |
01:25 |
x86 |
|
Microsoft.teamfoundation.build.server.logger.resources.dll |
10.0.40219.359 |
11,632 |
06-Nov-2011 |
01:25 |
x86 |
|
Microsoft.teamfoundation.build.workflow.dll |
10.0.40219.359 |
653,136 |
06-Nov-2011 |
01:25 |
x86 |
|
Tfsbuildservicehost.exe |
10.0.40219.359 |
192,800 |
06-Nov-2011 |
01:25 |
x86 |
References
For more information about the BuildTrackingParticipant class, visit the following MSDN website:
General information about the BuildTrackingParticipant class
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
