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));
            server.Authenticate();
            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)
{
    tfs.DestroyDeletedItem(item);
}

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.
Labels:

Comments

Post a Comment

Popular posts from this blog

Binding Enum with DescriptionAttribute in WPF

Binding an enumeration to a ComboBox can be done in several ways. In most cases you don't want to display the value itself, but a more user friendly description. One common approach is to use the DescriptionAttribute on the Enum values to supply a description for each value.  This is all possible in a very MVVM friendly way. First step is to add the  DescriptionAttribute  to the values of the enumeration. public enum MyValues { [Description("First value")] First, [Description("Second value")] Second } To retrieve the description from the enum we use a simple extension method. This method returns the value of the DescriptionAttribute if it exists, otherwise the string representation of the enum value is returned. public static string GetDescription(this Enum value) { var fieldInfo = value.GetType().GetField(value.ToString()); var attribute = fieldInfo.GetCustomAttributes(typeof(DescriptionAttribute), false).FirstOrDefault() as
2 comments
Read more

Programming AD with C#.NET – part 4

Our transition to the  System.DirectoryServices.Protocols  has in the whole gone very smooth, but there have been some issues with one environment that contains subdomains. Most things are working fine, but writing to a subdomain does not work in the same way as it did before. What is generally bad with the  System.DirectoryServices.Protocols is the documentation, which is practically non-existent. But most things can  be figured out anyway since most classes just are wrappers for the wldap32.dll, which in turn is way better documented. I would like to have as little bindings to a specific server as possible but still be able to access the domain. In the  LdapConnection  it is possible to set the identifier to null and use the executing computer as a starting point to find a domain controller. But sometimes I must know that I am using a Global Catalog, and with more and more RODC in the environment I sometimes must know that I am working against a writeable domain controller.
Post a Comment
Read more

User.Identity returns old login name after name change

When a person gets married or makes a name change for some other reason this usually means that the login name for the Active Directory-account changes as well. This is rarely a problem, but it turned out to cause some issues on our web server, where the  User.Identity  property was still returning the old login name. The user logged on with the new login name, but was identified by the web application as the old login name. The reason this occurs is because the  User.Identity  property relies on the  LsaLookupSids  method to convert the user SID to a login name. The method first calls the local  LSA-cache , which is not synchronized with the Active Directory. For this purpose a simple reboot of the web server to clear the  LSA-cache  propably would have sufficed. But since we didn't want to take the application offline rebooting was not an option. Instead, it is possible to set the registry value  LsaLookupCacheMaxSize in HKLM\SYSTEM\CurrentControlSet\Control\Lsa. If this val
Post a Comment
Read more