Tfs: how to unlock changes

Question

I originally edited the file in which the check was performed. I got a new computer, and now I want to edit the file. I'm not interested in the original editing.

TFS reports that another user has an exclusive file lock. Actually, this is not another user, it’s me, but the car is different, so the workspace is different.

I tried to unlock the tf command line using the following command:

tf lock / lock: none / workspace: oldmachinename; domain \ me / recursive $ / projectname / directory / s: http: tfs: 8080 / tfs / project

I have no errors, but when I switch to Visual Studio 2010 (we also use tfs 2010). Files remain locked.

What am I doing wrong?

Answer 1

Removing an old workspace is probably what you want to do. You can do this with the tf workspace command , but an easier way is to use the free TFS Sidekicks add-in , which gives you a graphical interface for managing and deleting workspaces.

Answer 2

Have you tried using TFS powertools ?

After that, you can right-click on your folder or file and select "Find in source control → status". After you click "Find", it should show you all statements or files that are uploaded

Then you can right-click on the checkout and select "Cancel ..".

Although this usually produces the same command line arguments, I got lucky with it.

Answer 3

If you are not going to use the old workspace again, it would be nice (carefully) to delete the entire workspace . This will clear everything related to it, and means that it no longer “pollutes” the lists of your active workspaces, etc.

You can also split the lock into one file, but you will need to have the appropriate permissions to be able to lock the locks. See here for a specific explanation of how to do this.

Answer 4

Try something like this:

The following example unlocks and makes all the files in the src / Team Foundation version control server folder available for registration and registration by other users.

c: \ projects> tf lock / lock: none src /

Additional documentation here: http://msdn.microsoft.com/en-us/library/47b0c7w9.aspx