In general, you can view the SharePoint site as the primary Web interface for your internal team and stakeholders. The SharePoint site focuses on artifacts related to the software solution you are creating, overall project process, and reporting. In addition, TSWA provides an easier way to bring in external stakeholders and users—in particular, those users who don't need access to SharePoint but might want to file a bug and track its progress.
This last feature is significant. With the release of Team Foundation Server , Microsoft modified the license agreement to allow any person to file a bug, track its status, or defect without the need for a client access license. However, TSWA doesn't offer an easy way to restrict access to features that could allow the user to accidently violate the license agreement for example, managing another user's work items. This update grants access to just the limited feature set allowed by the license change.
You can read the spec at go. This is just one example of updates planned under the Power Tools umbrella. As of press time, the March release is the most current. The collection of tools includes TFPT. It extends the built-in TF. Currently there are 19 supported commands see Figure 2. Depending upon the command you choose, you might be required to provide additional parameters.
Also, some of the commands, such as the rollback command, provide a GUI experience once you execute the command. Be aware that many of the commands require you to execute the tool from a folder that you've mapped to a TFS workspace.
For some users, this has been a long time coming. The big caveat I want to mention is that you must apply SP1 to your Visual Studio client installation in order for this command to work. Other commands that I find very useful in my work include rollback, treeclean, and workspace. Check them out for yourself. There's more goodness to be found related to version control in the Team Foundation Server Power Tools.
First, there's the custom check-in policies pack. This adds a number of useful check-in policies to your installation. Second, you'll find a number of enhancements inside Visual Studio. Annotate is one example. However, some other goodies still require the Power Tools. For example, you get the Find in Source command, Quick Label, and a simple but welcome feature that opens the selected folder in the Source Control Explorer in Windows Explorer see Figure 3. Each time you create a team project, you specify a process template.
Microsoft includes two out of the box. That said, I don't have a single customer who doesn't want to modify the base process templates. Most teams need to add additional fields to some of their work items, or they want to add their company logo to their reports, change the name of the Bug work item to Defect, or add their own docs to the SharePoint process guidance. Microsoft did a great job of exposing extensibility points to enable these kinds of customizations.
However, the out-of-the-box experience does leave something to be desired, unless you're editing process templates for a living. Without the Power Tools, you must download the process template to your local disk, put it under version control, and start editing the files. You can edit some files, such as your report definition files, using nice GUI designers like those provided in Business Intelligence Development Studio. 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. Back Next. Microsoft recommends you install a download manager. Microsoft Download Manager. Manage all your internet downloads with this easy-to-use manager.
It features a simple interface with many customizable options:. Download multiple files at one time Download large files quickly and reliably Suspend active downloads and resume downloads that have failed. Yes, install Microsoft Download Manager recommended No, thanks.
What happens if I don't install a download manager? Why should I install the Microsoft Download Manager? In this case, you will have to download the files individually.
You would have the opportunity to download individual files on the "Thank you for downloading" page after completing your download. Files larger than 1 GB may take much longer to download and might not download correctly.
You might not be able to pause the active downloads or resume downloads that have failed. These white papers describe the key capabilities of Microsoft Visual Studio Team System in greater depth. Details Note: There are multiple files available for this download. Once you click on the "Download" button, you will be prompted to select the files you need.
File Name:. Making Real-Time Decisions. Date Published:. File Size:. System Requirements Supported Operating System. Follow Microsoft Facebook Twitter.
0コメント