Perf Issue with TFS 2010 Build Log Viewer - by Ed Blankenship

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 630310 Comments
Status Closed Workarounds
Type Bug Repros 6
Opened 12/9/2010 7:49:51 PM
Access Restriction Public


Whenever opening a TFS 2010 build log that has lots of information nodes (such as builds with diagnostic verbosity) the WPF-based build log suffers from serious performance issues.  Additionally, if there are is a great number of warnings and/or errors the build summary view with have similar performance issues.

Update:  As Steve mentions, this is the in the Visual Studio build log viewer and not in the Team Web Access viewer.
Sign in to post a comment.
Posted by Adam [MSFT] on 2/1/2011 at 1:54 PM
We've fixed this in the upcoming VS2010 SP1 release. Build summary and details views will limit the number of errors and warnings listed to improve performance in scenarios when there are thousands of these. The full list is still available in the build log file.
Posted by Microsoft on 1/18/2011 at 8:54 AM
This bug has been fixed and should be in the next release of the product.
Thank you for reporting this issue.
Posted by Microsoft on 12/10/2010 at 1:18 AM
Thank you for your feedback, We are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(
Posted by Steve Godbold on 12/9/2010 at 7:53 PM
This applies only to viewing the build log in Visual Studio. When opening the build log via the tfs web access interface the performance is significantly better.