Search

Cannot Undo Pending Change by StuartRivenbark

Closed
as External Help for as External

1
0
Sign in
to vote
Type: Bug
ID: 777385
Opened: 1/24/2013 6:58:48 AM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
A user was trying to delete a folder in TFS just beneath the project node using the Source Control Explorer. They could not because the error message stated that an item in the project was locked by a user that has since left our employ. I tried to use the "tf undo" command, but it said there were no pending changes detected.

A closer observation revealed some interesting things. First, I turned on the option that allowed me to see folders that had been previously deleted. The error message mentioned above states that the locked file resides in a folder named "450SUM5". But, that folder had never existed in the project at any location.

The attached BMP file shows all of these issues clearly.
Details (expand)

Visual Studio/Team Foundation Server/.NET Framework Tooling Version

.NET Framework 4.0

Steps to reproduce

Not sure - I only have the end result.

Product Language

English

Operating System

Windows Server 2008 R2

Operating System Language

English

Actual results

The file cannot be unlocked.

Expected results

The error should not occur because the file never could have resided in the TFS project.
File Attachments
File Name Submitted By Submitted On File Size  
TFS_Bug.bmp 1/24/2013 3.75 MB
TFS_Bug.bmp 1/24/2013 3.75 MB
TFS_Bug.bmp 1/24/2013 3.75 MB
Sign in to post a comment.
Posted by Microsoft on 1/24/2013 at 8:07 PM
The product team itself no longer directly accepting feedback for Microsoft Visual Studio 2010 and earlier products. You can get support for issues with Visual Studio 2010 and earlier by visiting one of the resources in the link below:
http://msdn.microsoft.com/en-us/vstudio/cc136615.aspx
Posted by Microsoft on 1/24/2013 at 7:50 AM
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.