wietze/tfs-history-to-csv — explained in plain English
Analysis updated 2026-07-17 · repo last pushed 2017-12-18
Export a year of TFS changesets to CSV to see which developers touched which files.
Audit code history to check when specific files were last modified.
Prepare historical version control data as an intermediate step when migrating off TFS.
| wietze/tfs-history-to-csv | anton-petrov/rsabackdoor | darrelmiller/cowpi | |
|---|---|---|---|
| Stars | 1 | 1 | 1 |
| Language | C# | C# | C# |
| Last pushed | 2017-12-18 | 2015-01-20 | 2017-10-31 |
| Maintenance | Dormant | Dormant | Dormant |
| Setup difficulty | hard | moderate | hard |
| Complexity | 3/5 | 3/5 | 1/5 |
| Audience | ops devops | researcher | general |
Figures from each repo's GitHub metadata at analysis time.
Requires TFS and Visual Studio Professional (or better) plus .NET Framework 4.5+, Windows-only.
This tool converts Team Foundation Server (TFS) history into a spreadsheet-friendly CSV file. TFS is Microsoft's older version control system, think of it as a database that tracks every change made to code in a project. Instead of digging through TFS's interface to understand what changed and when, this tool pulls all that historical data and neatly packages it into a CSV file (the kind you can open in Excel) so you can analyze it however you want. The tool walks you through a simple three-step process. You run the executable, pick your TFS server and project from dropdown menus, then tell it where to save the resulting CSV file. Behind the scenes, it connects to your TFS server, retrieves every changeset (a bundle of changes someone made at one point in time), and exports the key details: who made the change, when they made it, what files they touched, whether they added or edited or deleted something, and any notes they left behind. You'd use this if you're auditing code history, analyzing team productivity, checking when certain files were last modified, or preparing historical data for migration away from TFS. For example, a team lead might export a year's worth of changes to understand which developers touched which parts of the codebase, or someone migrating to a newer system might need this data in CSV format as an intermediate step. The main limitation is that you need to have TFS and Visual Studio Professional (or better) installed on your machine, since the tool relies on Microsoft's TFS client libraries to connect and pull data. It's a Windows-only tool written in C#, and the README notes it requires .NET Framework 4.5 or higher.
A Windows tool that exports Team Foundation Server change history into a CSV file for easy analysis in Excel.
Mainly C#. The stack also includes C#, .NET Framework.
Dormant — no commits in 2+ years (last push 2017-12-18).
Setup difficulty is rated hard, with roughly 1h+ to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
Verify against the repo before relying on details.