Changeset 1

On occasion, I'm asked at work to look into an application with which I don't usually work. So, I go into Team Foundation Server, check it out, do my work, check it in, and go on with life.

After awhile though, the number of random mappings from TFS to my local machine start to bug me. It's not that I'm liable to run out disk space or, for that matter, because of anything significant. It just bugs me.

I used to go to Windows Explorer, open up the folder that mapped to the root of my TFS workspace, and then navigate downward until I found the offending folder, and delete it.

This works to a point: sure, when you're breezing through source control you no longer see random folders checked out or marked as being the latest. But, if you ever need to go back and get some or all the files again, TFS won't because you haven't told TFS you removed the local files!

If you truly want to remove the files and make sure TFS knows it, then you should get changeset 1. Changeset 1 is a special changeset that removes the local files and tells TFS you've done so.

This is an easy process. Simply follow the steps below.
  1. From within Visual Studio, open Source Control and navigate to the folder you wish to remove.
  2. Right-click on the folder and select Advanced — Get Specific Version...
  3. When the Get dialog appears, set "Type" (within the "Version" portion of the dialog box) to "Specific Version" and set the changeset to 1, as shown here:
  4. Click the Get button.
  5. Voila! TFS will do its thing and you'll find that the local files are gone.

Comments

Post a Comment

Popular posts from this blog

Using Reference Aliases

Image
I recently ran across a situation where two different libraries shared identical namespaces and class names. Visual Studio complained anytime I used one of these classes that it was an ambiguous reference. I needed both libraries -- each contained some unique elements -- so I couldn't ditch one or the other. But, as I said, anytime I tried to use a class that was common (again, via the class name and namespace), I received the ambiguous reference error. This was a real problem, so say the least. However, C# provides a way to specify exactly which library (reference) you mean when you use an object that's common to two or more libraries. Simply put, you use an extern alias  statement. The concept is fairly simple: Give the reference an alias (I used the Properties windows for the reference). Add an extern alias statement, putting it before your using statements. Add a using statement, which effectively links a specific object through the extern alias statement to th
Read more

List of Visual Studio Keyboard Shortcuts

Here's a link to a great list of keyboard shortcuts for Visual Studio: 149 Shortcuts for Visual Studio 2015 (Windows) While there's no need to memorize the list (that's why someone has created a cheat sheet, after all), it certainly doesn't hurt to look over the list from time to time and try to add one more command to your repertoire.
Read more