Skip to main content

Destroy old data in TFS

Team Foundation Server only performs soft deletes and the files are very easy to recover just by performing an undelete. After a while the deleted files may use a lot of unneccesary space. From TFS 2008 it is possible to erase the data from the database. On option would be to use tf.exe and the destroy command. That however will be pretty tedious when there is more than one file that should be destroyed. I have created a small application to help with this task.

The TFS communication is handled in a separate class which i very simple without any error handling.

using System;
using System.Net;
using System.Windows.Forms;
using Microsoft.TeamFoundation.Client;
using Microsoft.TeamFoundation.VersionControl.Client;
using Microsoft.TeamFoundation.VersionControl.Common;

namespace TFSCleanupTool
    internal class TFS
        private string ServerName = null;
        private VersionControlServer VersionControl = null;

        internal TFS(string servername)
            ServerName = servername;

        internal void Connect(string domain, string username, string password)
            TeamFoundationServer server = new TeamFoundationServer(ServerName, new NetworkCredential(username, password, domain));
            VersionControl = (VersionControlServer)server.GetService(typeof(VersionControlServer));

        internal Item[] GetDeletedItems(string path)
            ItemSet itemSet = VersionControl.GetItems(path, VersionSpec.Latest, RecursionType.Full, DeletedState.Deleted, ItemType.Any);
            return itemSet.Items;

        internal void DestroyDeletedItem(Item item)
            ItemSpec itemSpec = new ItemSpec(item.ServerItem, RecursionType.Full, item.DeletionId);
            VersionControl.Destroy(itemSpec, VersionSpec.Latest, null, DestroyFlags.None);

Usage of this class is very simple and this is just sample.

TFS tfs = new TFS("server");
tfs.Connect("domain", "username", "password");
Item[] items = tfs.GetDeletedItems("$/");
foreach(Item item in items)

This class only handles already deleted files. It is possible to destroy non-deleted files as well, but I do not really see the point in that. Keep in mind that the data will be permanently removed and cannot be restored, so be careful! Always back up the TfsVersionControl database before using the destroy methods.


Popular posts from this blog

Binding a HTML-formatted string to a WPF WebBrowser control

Sometimes there is a need to display a HTML formatted string in a WPF application. There are a couple of ways to do this, but the most stright forward is to use a WebBrowser control and the NavigateToString method.

This approach has one big flaw, you cannot use binding to a string out of the box, but I found a great solution through Stack Overflow which adds a bindable property to the  WebBrowser control using  NavigateToString.

The following class is all that is needed to add that behavior. A new depencency property named Html is introduced to the  WebBrowser and the proper change action is performed in the OnHtmlChanged method.

public class BrowserBehavior { public static readonly DependencyProperty HtmlProperty = DependencyProperty.RegisterAttached( "Html", typeof(string), typeof(BrowserBehavior), new FrameworkPropertyMetadata(OnHtmlChanged)); [AttachedPropertyBrowsableForType(typeof(WebBrowser))] public static string GetHtml(WebBrowser browser) { …

Using Bootstrap Tooltip to show Parsley validation errors

I'm currently working on a web application using a variety of different frameworks, such as Backbone for the back-end, Bootstrap for the front-end and Parsley for client side form validation. Parsley is a really powerful validation toolkit, but it takes some tweaking to make it blend with the Bootstrap front-end. Fortunately this is a one time fix, which can be re-used all over our project.

Since there will be some custom options in our Parsley object, we can't use the default parsley-validate attribute on the form. Instead we have to initialize the validation with the jQuery syntax:

The options are were the magic happens, and in our case we have a global options object that our forms use to get the same experience all over the application. Here's what it looks like:

var parsleyOptions = {  // Sets success and error class to Bootstrap class names  successClass: 'has-success',  errorClass: 'has-error',  // Bo…

jQuery file upload with Bootstrap progress bar

Performing an asynchronous file upload from the browser is a common problem with almost as many solutions as there are developers. The following solution is the best fit for my needs, and also works well with most popular browsers. Backwards compatibility is not an issue in this case which is great, because I can use the new technologies as they are supposed to be used.

Everything is put together in JSFiddle for a working example. I will continue to explain the parts below...

First, the input field needs to be styled as a button. The form tag is only present for us to be able to reset the file input field later on.

<form>     <span class="fileUpload btn btn-default">         <span class="glyphicon glyphicon-upload"></span> Upload file         <input type="file" id="uploadFile" />     </span> </form>
.fileUpload { position: relative; overflow: hidden; } .fileUpload input { position: absolute; …