Search related threads. Remove From My Forums. Answered by:. Archived Forums T-U. Sign in to vote. Install on. Supported Server Version s. Check-In Policies. Match each client version. Match server version. Not supported on Win10 with Express for Windows. TE Enhancements. Team Members. Commands broken out in rows below:. Varies by command. The exception to this rule is the Windows extensions, where as a limitation of the operating system, the most recent version you have installed will always be used.
If you were using an old version of the check-in policies PowerTool and plan to upgrade your Team Foundation Server and PowerTools to the version, your changeset comments, work item associations, and code analysis check-in policy should continue to work, as long as you were using a compatible version of Visual Studio Visual Studio , Visual Studio , Visual Studio or Visual Studio Sign in. Power Tools are a set of enhancements, tools, and command-line utilities that increase productivity of Team Foundation Server scenarios.
Support for Visual Studio Express Visual Studio Express editions are now supported with the exception of the following features: addprojectportal, addprojectreports and createteamproject. It adds the following checkin policies: Policy Description Custom Path Policy This policy scopes other policies to specific folders or file types Forbidden Patterns Policy This policy prevents users from checking in files with fobidden filename patterns Work Item Query Policy This policy allows you to specify a work item query whose results will be the only legal work items for a check-in to be associated with Process Template Editor A Visual Studio add-in, located under the Tools menu.
Storyboard Shapes This tool enables you to create shapes for the PowerPoint storyboarding add-in with custom resize logic. Team Explorer Enhancements This tool provides additional Visual Studio menu options and functions to support finding files under version control by status or wildcard, opening a folder using File Explorer from the Source Control Explorer context menu, and labeling files and folders in Source Control Explorer.
This tool addresses these issues by: 1. Determining which set of diagnostic captures is taking up how much space AND 2. Windows PowerShell Cmdlets This tool provides a Windows PowerShell interface that supports basic version control commands and a pipeline and glue to enable scripting.
Windows Shell Extensions This tool provides integration with Windows Explorer and the common file dialogs. Compatibility Matrix The following table explains how to decide which version of each PowerTool to use and where to install it. Other files types, however, like the ever-popular work item type definition files, require you to fire up Notepad or your favorite XML editor and begin hacking angle brackets. This is not the best experience if it's your first time modifying process templates.
Thankfully, the Power Tools include a process template editor. This tool allows you to edit your downloaded template's components on disk or, against my general advice, you can edit some items such as work item type definitions online.
For example, you can open the Scenario work item type from the Microsoft Solutions Framework for Agile Software Development version 4 template, define a new field for tracking your beverage of choice to drink once you ship a feature described by the scenario, then add this field to the work item layout, and get a preview of the change see Figure 4 , all without seeing any XML.
That said, as you become more comfortable with process template modifications, you might find that editing the XML files directly is more convenient. The good news is the Process Editor helps there, too. A big enhancement in the March release is updated support in the editor for adding custom controls to your work item type definitions. Prior to this release, you would receive an error if you opened a work item type definition that used custom controls.
Another feature related to work items in the Power Tools is work item templates. You create a work item template containing common default items for a particular work item type. Then when you need to open a new bug, for example, you select the template, and it will prepopulate the work item for you.
Enhancements in the March release include work item templates having their own node in the Team Explorer window. These posts include data such as the number of items under version control, the server uptime, and the number of users. This tool provides an easy way to gather your own statistics on TFS usage for your development team.
It then analyzes the information using specific rules and gives you the results in the form of information, warning, or error messages. Beyond that it provides links to articles to help you resolve any warning and error situations. This tool is useful both as a preinstallation step as well as for helping you maintain and monitor your TFS installation.
This tool runs in the Windows task bar's notification area. You configure it to monitor a specific set of build definitions on your TFS installation.
You then tell it to notify you based on various events including when a build is queued, started, or completed.
When one of the events occurs, such as a build is queued up, you'll receive a message in the lower-right corner of your screen see Figure 5.
All of the tools that I've referenced are great. Some, however, can adversely affect your local machine or server installation anything with destroy comes to mind. Wouldn't it be nice to try things out where you wouldn't affect your real work environment?
You can also select View Build Status menu option and check the status of the build. You are commenting using your WordPress. You are commenting using your Google account. You are commenting using your Twitter account. You are commenting using your Facebook account. Notify me of new comments via email. Notify me of new posts via email.
0コメント