Welcome to the TFS Productivity Tools project

This package was written as a part of a job in Experis.

The TFS Productivity Tools project was designed to provide TFS administrators with helper extensions for Source Control or Work Item Tracking tasks.

For running these extensions the installation of Visual Studio Professional is required.
The extensions was tested with Visual Studio 2012 only.

Installation

For installing anyone of the extensions double-click on VSIX file and follow the installer instructions.

ChangeLinkTypes

This extension modifies link types between the Work Items returned from Work Item query.
To execute it select any query under Work Items node in Team Explorer window and click on "Change Query Link Types".

After that, in next dialog choose original and new wanted link types.

DestroyWorkItems

This extension completely destroys (not closes) Work Items returned from Work Item query.
To execute it select a number of Work Items in Query Results window and click on "Destroy Work Items".

Export2Word

This extension exports Work Items returned from Work Item query to Microsoft Word document in paragraph style. It uses MS Office Interop package and requires a local installation of Word.
To execute it select any query under Work Items node in Team Explorer window and click on "Export to Microsoft Word".

ExtendedMerge

Extended Merge extension provides workaround for several merge features not implemented by TFS:

1. TFS merge leads to bulk check-in operation that puts files from all previous changesets into one big merge changeset.
2. TFS allows only for consecutive changesets being cherry-peeked by merge operation.
3. TFS doesn’t allow choosing changesets for cherry-peek merge by selecting work items.
4. TFS merge dialog doesn’t have “force” and “baseless” options.

Initializing ExtendedMerge extension

The list of merge candidates can be obtained in two ways:

1. From Source Control Explorer window.
   In this case all history changesets for a specific server path are parsed.
   
2. From Query Results window.
   In this case all changesets, linked to the selected Work Items are parsed.
   

After initialization stage extension opens Visual Studio tool window pane with a grid that shows useful information about parsed changesets:

• Checked/unchecked status.
• Work item ID.
• Changeset ID.
• Changeset check-in date
• Changeset creator.
• The change types this changeset contains.
• Possible merge options
  • None – merge is impossible (don’t mess with “discard” commandline option)
  • Baseless – baseless merge
  • Force – force merge
  • Candidate – regular merge
• Merge source path (can be modified).
• Changeset comment field.

The Merge Target Location field contains the path to a folder or a branch in source control.

Merge types are calculated based on shared Merge Target Location path and an individual changeset Source Path.

Running ExtendedMerge extension

Extension runs all actions from toolbar buttons (some of them are duplicated on grid context menu also).

Resolving merge conflicts

During merge operation merge conflicts can occur.
In this case click on OK button and resolve conflicts with standard TFS Resolve Conflicts dialog.

GetPreview

This extension emulates TFS commandline operation: tf.exe get /recursive /preview "itemspec"
To execute it select a path in Source Control Explorer window and click on "Emulate Get-Preview".

The results are print to Output window.

ModifyCheckinDate

This extension consists from 2 parts:

1. Updates modification time for checked-out files to their latest check-in time.
   It is accessible from Source Control window & History window.
2. Directly modifies changeset's check-in time in TFS database.
   It actually runs SQL statement: UPDATE tbl_Changeset SET CreationDate=’?’ WHERE ChangeSetId=‘?’
   It is accessible from History window.

Release Notes

The ExtendedMerge uses a number of internal Microsoft classes. It can possibly lead to some tool malfunction in the next TFS versions: