Power Tools and MSSCCI provider for TFS 2010 Beta 2

by Ewald Hofman 1. December 2009 11:55

Today Microsoft has released the first two extensions on TFS:

  • MSSCCI provider
  • TFPT

MSSCCI provider

With the MSSCCI provider, you can connect to TFS Version Control with environments other then Visual Studio 2008/2010. This provider has shown its relevance to have great adaptation in the previous power tools. Having this provider for the TFS 2010 Beta 2 version makes the decision to use TFS 2010 in the beta 2 phase even more easy for companies.

You can find the download at http://visualstudiogallery.msdn.microsoft.com/en-us/f959ea32-5ac3-424a-a709-5001a158ebe8


The TFPT are the power tools for TFS. When I go to a customer, first thing I recommend is to install the power tools. I can not live without them anymore!

The following table lists the features that are available in the power tools

Power tool Description
Process Template Editor (PTE) You can change the process template and the work item types (WIT) without the power tools with the command line. With the PTE, you have access to a visual editor with the Tools menu in Visual Studio. This makes it much easier to customize the process template to your specific needs.
Best Practice Analyzer (BPA) The BPA checks your TFS installation on the recommended settings. As a TFS administrator, you will love this tool since it will tell you how you can improve the health of the configuration.
Check-in policy pack

Check-in policies are extremely helpful in guiding the TFS users what is required when they check in their code. Installing the check-in policies improves the quality, the traceability and the stability of the versioned items. Included in the power tools are:

- Custom Path Policy, which makes it possible to apply a check-in policy on specific version control folders
- Forbidden Patterns Policy, which disallows to check-in filenames of a specific pattern
- Changeset Comments Policy, which ensures that the comment is entered when checking in
- Work Item Query Policy, which ensures that a work item is included that is part of a work item query

Windows Shell Extension Not everybody wants to work with Visual Studio to be able to put files under version control, like a requirements engineer or a tester. With this extension, the context menu of the Windows Explorer contains the version control menu items (such as get latest, check in and check out). The menu items will appear in the menu for every folder that is included in a workspace.
PowerShell support PowerShell gives you an alternative to programming in C# against the TFS SDK. It is a great tool for administrators to automate tasks.

Command line support

TFPT has the ability to perform most actions by the command line

Work Item Templates

With these templates you have the ability to populate work items with default values. For example, when you are creating lots of work items for a specific person for a specific area in a specific iteration, you can add these values to the template and create work items from the template, or apply the template to already created work items

Alert editor

TFS has a built-in alert editor, which is very limited in functionality. With the alert editor, you can define the condition when the alert should be triggered with a nice UI.

You can find the download at http://visualstudiogallery.msdn.microsoft.com/en-us/0e69a28f-020c-488b-80b3-f4c89a20621d

Tags: , , , ,

VSTS 2010

Use Powershell to execute a TFS console app for each team project

by Ewald Hofman 7. September 2009 23:18

I wanted to remove one of the field mappings for MS Project for all team projects. Of course I could create a simple batch file and then retrieve all team project names from somewhere and copy the command several times. But as a real IT guy: I am lazy.

So I wanted to automate the process. Of course I could have used the TFS API, but then you have to start visual studio, put in the same code over and over again. I wanted to explore new fields, being Powershell.

There is a lot of information about powershell on the web. An excellent blog is from James Manning. But you can also see the Powershell help on Technet.

This post covers the execution of the TFSFieldMapping.exe on all team projects to upload new field mappings.

Step  Descriptio 
To be able to iteraterate through the team projects, we need to make a connection to TFS. There is an excellent script, created by James Manning, called get-tfs, which you can find at: http://blogs.msdn.com/jmanning/archive/2006/09/28/776141.aspx  
2 Download the script and place it in the same directory as your script will be saved.
3 Create a new file called UploadMappings.ps1
4 Open the file in notepad
5 Enter the contents (see below) in the file
6 Save the file
7 Open the command prompt
8 Type Powershell
9 Go with cmd "my dir" to the directory where your script is located
10 Type .\UploadMappings

The full script looks like



 $cmd = """c:\program files\Microsoft Visual Studio 9.0\Common7\IDE\tfsfieldmapping.exe""";
 $server = "[TFS URL (eg. http://mytfsserver:8080)]";
 $tfs = .\get-tfs $server;
 $css = $tfs.css;
 $mappingfile = "[location of mapping file]";

 $css.ListAllProjects() | % {
  "Upload fields for $_";
  $info = new-object System.Diagnostics.ProcessStartInfo;
  $info.FileName = $cmd;
  $info.Arguments = "upload $server ""$_"" $mappingfile";
  $info.UseShellExecute = $false;
  $p = [diagnostics.process]::start($info);


VSTS 2008

Powered by BlogEngine.NET
Theme by Mads Kristensen


Widget Statistics not found.

There is an error in XML document (0, 0).X

Recent comments

Comment RSS