Visual Studio 2005 Team Foundation Server Power Tools
Visual Studio 2005 Team Foundation Server Power Tools is a set of enhancements, tools and command-line utilities that improve the Team Foundation Server user experience.
This release includes everything from the previous Power Tools release and includes two great new tools, the Team Foundation Server Best Practices Analyzer and Work Item Templates.
Team Foundation Server Power Tool (tfpt.exe) is a command-line tool. To use these commands, start tfpt.exe at the Command Prompt. Some of the commands will display a graphical user interface when used. In addition, you can access the Annotate and Treediff commands from Source Control Explorer in Visual Studio or Team Explorer. Team Foundation Server Power Tool includes the following commands:
Unshelve Command Use the unshelve command to unshelve and merge the changes in the workspace.
Rollback Command Use the rollback command to roll back changes that have already been committed to Team Foundation Server.
Online Command Use the online command to create pending edits on writable files that do not have pending edits.
GetCS Command Use the GetCS (Get Changeset) command to get the changes in a particular changeset.
UU Command Use the UU (Undo Unchanged) command to undo unchanged files, including adds, edits, and deletes.
Annotate Command Use the annotate command to download all versions of the specified files and show information about when and who changed each line in the file.
Review Command Use the review command to optimize the code review process to avoid checking in or shelving.
History Command Use the history command to display the revision history for one or more files and folders. The /followbranches option returns the history of the file branch’s ancestors.
Workitem Command Use the workitem command to create, update, or view work items.
Query Command Use the query command to run a work item query and display the results. If you do not provide a specific query, all the active work items assigned to you are displayed.
TreeDiff Command Use the treediff command to display a visual representation of the differences between files in two server folders, in a server folder and a local folder, or in two local folders.
Treeclean Command Use the treeclean command to view and optionally delete files that are not under source control in the current directory and all subdirectories. This command is useful when you want to remove temporary files from your local workspace, such as files created by the compiler.
>Return to Top of Page
Team Foundation Server Power Tools installs Visual Studio Team System Process Editor, which is a process template editor for editing Team Foundation Server process templates inside the Visual Studio IDE. The installation media includes separate documentation for the Visual Studio Team System Process Editor, which includes a User Guide and a Readme file that includes known issues.
NoteTo use the Team System Process Editor, you must first install the Domain-Specific Language Tools for Visual Studio 2005 Redistributable Components.
Team Foundation Server Power Tools also installs a set of check-in policies. The custom policies include:
Custom Path Policy Works with existing Team Foundation Server check-in policies. It provides a mechanism that lets you specify the source control path or paths upon which a particular policy acts. This initiates a scenario where you can enforce a different sets of rules for different source control folders. For example, one folder can have more stringent code analysis policy rules applied than another folder
Forbidden Patterns Policy Allows you to specify a file extension or a regular expression that you can use to keep certain file types from being checked in to source control. This policy is most useful for DLL-files, build artifacts, or automatically-generated Web site files that are generated automatically during development. Versioning these files is not appropriate since they are on demand and specific to the development environment. The Forbidden Patterns policy scans each of the file names on check-in. It determines if there is a match. If there is a match, the check-in is blocked.
Changeset Comments Policy The Changeset Comments policy allows you to verify that the Comments text box in the Check In dialog box is not empty. You cannot check in a file if the Comments text box is empty.
Work Item Query Policy The Work Item Query policy allows you to specify a team query to which the work item associated with a check-in must belong. If the results of the query do not include the work item associated with the check-in, check-in is blocked.
In Visual Studio Team System, you must specify test metadata files (.vsmdi files) when you run tests as a part of a build type. The TestToolsTask installed with TFPT extends the original TestToolsTask to support the specification of test containers in addition to the specification of test metadata files. When you specify a test container to be used with the new TestToolsTask, the system runs all tests in the test container. This functionality is the same as running the mstest.exe command-line application with the /testcontainer option specified. For more information, see Command-Line Test Execution.
This release of the Team Foundation Power Tools includes the first release of the Team Foundation Server Best Practices Analyzer (Team Foundation Server BPA). The Team Foundation Server BPA is a diagnostic tool that performs the following functions:
You can use the Team Foundation Server BPA in either a pre-installation or a production Team Foundation Server environment. You can use the Team Foundation Server BPA to perform the following tasks:
Team Foundation Power Tools installs a Work Item Templates feature that supports the ability to create, apply, capture, and set default work item templates. This feature adds additional menu items to the Team Work Item Templates menu.
You use work item templates to create or update work items. Work item templates automatically set field values. This feature conveniently reduces the number of steps to create or update work items. For example, you can create a task template that will set the area path, iteration path, and discipline whenever you use it to create or edit a task.