Working with Changesets (Team Explorer Everywhere)

  • Article

You use a Team Foundation version control changeset to store and find information about a single check-in operation. When you check in your pending changes, a changeset is created that stores information about file and folder revisions, links to related work items, check-in notes, a comment, policy compliance, and system metadata such as owner name and date/time of check in.

In this topic

Required Permissions

To perform this procedure, the Read permission on at least one file that you are trying to find must be set to Allow. For more information, see the following topic on the Microsoft Web site: Team Foundation Server Permissions.

View Detailed Information for a Changeset

You can get the following historical information about one or more changesets:

  • which files were changed

  • what the exact changes were

  • who changed the files

  • what the check-in comment contains

  • which work items are associated with the changeset

  • which policy warnings appeared

To view information about a changeset

  1. In Project Explorer or Package Explorer, right-click anywhere, point to Team, and click Go to Changeset.

    The Go to Changeset dialog box appears.

  2. Perform one of the following tasks:

    • In Changeset, type the changeset number and click OK.

      The details for the specified changeset appear.

    • Click Find to search for a changeset and view its details. For more information about how to search for a changeset, see Search for a Changeset.

To view information about a changeset from a command prompt

  1. Open a command prompt.

  2. Type tf changeset ChangesetNumber and press ENTER. Replace ChangesetNumber with the number of the changeset for which you want to view information.

    For more information about the changeset command, see the following page on the Microsoft Web site: Changeset Command (Team Foundation Version Control).

Retrieve Previous Versions of Files from Changesets

One of the ways in which you can retrieve a specific version of files is by retrieving the version that was submitted in a specific changeset. For information about other ways in which you can retrieve specific versions of files, see Update File Versions in Your Workspace (Team Explorer Everywhere).

To retrieve the version of a file that was submitted in a changeset

  1. Perform one of the following tasks:

    • Open Source Control Explorer. For more information, see Using Source Control Explorer (Team Explorer Everywhere).

      In Source Control Explorer, right-click the folder or file for which you want to update the version to the local workspace and click Get Specific Version.

    • In Project Explorer or Package Explorer, expand the Eclipse project for which you want to update files or folders. Right-click the file or folder that you want to update, point to Team, and click Get Specific Version.

    The Get dialog box appears.

  2. In the Version list, click Changeset.

    Changeset fields appear.

  3. Perform one of the following tasks:

    • In Changeset, type the number of the changeset.

    • Click Browse (...) to search for a changeset. For more information, see Search for a Changeset.

  4. Click Get.

    The version of the files that were submitted in the specified changeset is retrieved to your local folder.

To retrieve the version of a file that was submitted in a changeset from a command prompt

  1. Open a command prompt.

  2. Perform one of the following tasks:

    • To retrieve the version of all uncloaked items from the server as they existed on the server when a changeset was created, type tf get -version:CChangesetNumber and press ENTER. For example, you could type tf get -version:C1999.

    • To retrieve the version of a single uncloaked item from the server as it existed on the server when a changeset was created, type tf get Filename;CChangesetNumber and press ENTER. For example, you could type tf get Class1.java;C1999.

    For more information about the get command, see the following page on the Microsoft Web site: Get Command (Team Foundation Version Control).

Search for a Changeset

You can search for a changeset either to view changeset details or if you want to get a specific version of one or more files. This procedure assumes that the Find Changesets dialog box has appeared. For information about how to open the Find Changesets dialog box, see View Detailed Information for a Changeset or Retrieve Previous Versions of Files from Changesets.

To search for a changeset

  1. In Project Explorer or Package Explorer, right-click anywhere, point to Team, and click Go to Changeset.

    The Go to Changeset dialog box appears.

  2. In Changeset, click Find.

  3. In the Find Changesets dialog box, you can search for changesets by using any of the following techniques:

    • In Containing file, type the file name.

      You can also click the Browse button to search for the file.

    • In By user, type the name of the team member.

  4. Under Range, specify in which changesets to search for the file, the user, or both:

    • All changes Searches all changesets.

    • Changeset number Searches for a changeset whose number is in a specific range. Click Changeset number, and then type the range of changeset numbers to search.

    • Created date Searches for changesets that were created during a specific time period. Under Created date, specify a starting and ending date.

  5. Click Find.

  6. To display the details for a changeset, in the Results list, click a changeset and then click Details. You can change to the changeset details and then click Save.

  7. If you opened the Find Changesets dialog box from the Get dialog box, click OK to accept the highlighted changeset as the version of the files that you want to retrieve. Otherwise, click Close or Cancel.

See Also

Tasks

Find, Link, and View Changesets Associated with a Work Item (Team Explorer Everywhere)

Other Resources

Submitting and Undoing Pending Changes (Team Explorer Everywhere)

Working with Team Foundation Server Workspaces (Team Explorer Everywhere)