PowerShell Script Provides Simple Change History File

,

External code audit? Need a list of TFS file changes during a specific time frame?

Consider using a PowerShell script.

While history in TFS can provide a list, it does it by changeset, not by file. To see it by file, only one file can be seen at a time. PowerShell script can get the change history of a project using TFS version control as a CSV file. This tool allows you to get a list of all changes including filename and date changed. It works for Team Foundation Version Control (TFVC).

This is a simple script that calls the TFS API to get the history of all files in the project. It pulls the changesets and then expands to all files touched. The results are exported to a file (default name is FileHistory.csv) in a CSV format in the current folder.

Output Format

The CSV format has the following columns:

  • FileName: The source control path of the file that was changed
  • ChangeSet: The ChangeSet that contains the change
  • Author: User who checked in the change
  • Date: Date the ChangeSet was checked in
  • Comment: Comment on the check-in
  • ChangeSetLink: Web link to the ChangeSet
  • FileLink: Web link to this version of the file

Command Line Parameters

There are a number of command line parameters:

  • server: URL of the server. http://[host]:[port]/tfs/[collectionname]
  • fromDate: Date to start looking for changes. M/D/YYYY. 11/1/2017
  • toDate: Date to stop looking for changes. M/D/YYYY. 12/1/2017
  • path: Project and path to search for changes in. Electron/dev
  • maxCount: Maximum number of changesets to bring back (default: 1000)
  • outFile: Filename for results. (default: FileHistory.csv)

Example

Note that you can also modify the file with parameter defaults for the server and path that you access regularly.

Share this story