Skip to main content

Automatically configure Team Explorer connections

The first time you open Team Explorer to connect to Team Foundation Server there are three things that needs to be done before you can start working against the server.
  1. Register server in Visual Studio
  2. Select active projects in Team Explorer
  3. Create workspace in Source Control
I got a request if there was a way to automate these steps. Of course it can be done, but there are some light hacking involved. Here is what I cam up with:

Register server
Registered servers are easy to manage since they are saved in the registry. Given that the user has write access to the registry this step is easy to automate. The structure is as shown below, where my server is called ServerName. The key names explain themselves and this is all that is needed for Visual Studio to find the server as a registered Team Foundation Server.

[HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\9.0\TeamFoundation\Servers]
"ServerName"="http://servername:8080/" 

[HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\9.0\TeamFoundation\Servers\ServerName]
"Offline"=dword:00000000
"AutoReconnect"=dword:00000001

Select active projects
Active projects are saved in the Team Explorer configuration file. This is save to one of the following locations:

Windows 7
C:\Users\{user}\AppData\Roaming\Microsoft\VisualStudio\9.0\Team Explorer\TeamExplorer.config

Windows XP
C:\Documents and Settings\{user}\Application Data\Microsoft\VisualStudio\9.0\Team Explorer\TeamExplorer.config

The file only contains a list of the active projects with an URI reference. That makes it pretty straight forward to create or modify this file as you wish. This assumes that the user has write access to the specified directory.

<!--Configuration file: specifies which project are visible in the Team Explorer-->
<server_list>
    <server url="http://servername:8080/" current="yes" autoload="yes">
        <project uri="vstfs:///Classification/TeamProject/74ef7e04-e96a-4bc1-9f4f-307d92eb5666" />
        <project uri="vstfs:///Classification/TeamProject/eff01aeb-6d20-4523-a3e2-8709c88319fc" />
        <project uri="vstfs:///Classification/TeamProject/0f8f3f94-e63b-4401-aa5a-014b079e156d" />
    </server>
</server_list>

Create workspace
Creating a workspace is the only of the steps that is made by using the Team Foundation Server API. Here is a simple example of how it may look. VersionControl is a property of the type VersionControlServer that has already been initialized.

internal void CreateWorkSpace(string sourceControlPath, string localPath)
{
    if(!Directory.Exists(localPath))
    {
        Directory.CreateDirectory(localPath);
    }
    WorkingFolder[] workingFolders = new WorkingFolder[]
    {
        new WorkingFolder(sourceControlPath, localPath, WorkingFolderType.Map)
    };
    VersionControl.CreateWorkspace(WorkSpaceName, UserName, String.Empty, workingFolders, SystemInformation.ComputerName);
}

With these steps packed together in a neat little application run at logon the user never has to anything more than to start Visual Studio to get started working against the Team Foundation Server.

Comments

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

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

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.