Select the product you need help with
A hotfix rollup (build 10.0.40219.359) is available for Team Foundation Server 2010 SP1Article ID: 2632377 - View products that this article applies to. On This PageIntroductionA 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 1When 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 2When 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 3When 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:Note When this issue occurs, most of the build steps that are processed are unnecessary. CAUSECause of Issue 1This issue occurs because the build tracking participant that is added to the extension of the workflow application is deleted incorrectly.Cause of Issue 2This issue occurs because the downloaded files do not have the same name as the original files.MORE INFORMATIONThe 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:
RESOLUTIONTo 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=support Note 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.
(http://support.microsoft.com/contactus/?ws=support)
PrerequisitesTo apply this hotfix rollup, you must have TFS 2010 SP1 installed.Restart requirementYou do not have to restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace a previously released hotfix.File informationThe 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.Collapse this table
REFERENCESFor more information about the BuildTrackingParticipant class, visit the following MSDN website: General information about the BuildTrackingParticipant class
(http://msdn.microsoft.com/en-us/library/microsoft.teamfoundation.build.workflow.tracking.buildtrackingparticipant.aspx)
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. PropertiesArticle ID: 2632377 - Last Review: November 24, 2011 - Revision: 1.0
| Article Translations
 |
Back to the top
