Home Dashboard Directory Help
Search

"An item with the same key has already been added" from Builds view of Team Explorer by NIGregR


Status: 

Resolved
 as Duplicate Help for as Duplicate


2
0
Sign in
to vote
Type: Bug
ID: 779288
Opened: 2/15/2013 6:36:32 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

I am running Visual Studio 2012 Update 1 against a TFS 2010 server. When certain combinations of builds are added to the "My Favorite Build Definitions" section of the Builds view of the Team Explorer, I get the message "An item with the same key has already been added". When this happens nothing in the view will update. "My Builds" and "My Favorite Build Definitions" just continue to show the last status they had before adding the new definition. Removing the last definition from favorites corrects the problem.

I found this report "http://connect.microsoft.com/VisualStudio/feedback/details/778725/tfs-2012-agile-6-1-template-problem-an-item-with-the-same-key-has-already-been-added" that mentioned the same error message. It was supposedly fixed in U1 which I have but I tried clearing the cache as it suggested. Now when I launch VS the Builds view does not populate any sections. This means I can't even correct the problem because there are no builds in the favorites section.
Details
Sign in to post a comment.
Posted by Microsoft on 2/22/2013 at 6:48 AM
Thank you for reporting this issue. We have fixed this bug in the latest CTP available for VS 2012 Quarterly Update 2. It is available for download:
http://blogs.msdn.com/b/visualstudioalm/archive/2013/01/30/first-ctp-for-visual-studio-update-2.aspx
Posted by Microsoft on 2/19/2013 at 11:15 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by Microsoft on 2/18/2013 at 11:10 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.