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

Comments

Post a Comment

Popular posts from this blog

Moving to the cloud - part 1

I cannot with words describe the hype around the cloud today, and of course I had to join the croud. I have transferred all my applications, files and services to the cloud. I thought I would share some of the experiences and difficulties I have hit during my jourey. These are the steps I have performed in order to complete my move to the cloud: Most of my files are safely stored with  Dropbox . E-mail accounts for stodell.se  were moved from service provider to  Google Apps . The Cornball was moved from service provider to  Windows Azure och SQL Azure . This blog was moved from Wordpress at a service provider to  Google's Blogger . Even though  Loopia has been a great service provider during many years I have now been able to cancel all my services except the domain hosting with them. The replacement being free services and the Azure capacity that is included in the MSDN subscription.
Post a Comment
Read more

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 bro
1 comment
Read more

Getting started with Silverlight

In my work with the Cornball as my first Silverlight project I have had to solve a huge amount of problems which turned out to be quite a high threshold before I could get started with the development for real. Not the least in the difference between a WinForms application and a Silverlight application. In this post I will mention a couple of the things i encountered. Splash Screen/Preloader The builtin preloader in Silverlight does not look too bad, but it is definately more fun to create a custom preloader to fit with the rest of the application. I choose to create a very simple but functional preloader. First I had to include all the images as resources in the application for the preloader to actually have a purpose. By adding the images to the project and select Resource as Build Action the images will be included in the XAP-file. To show the images in the application, something of the following will do. XAML <Image Name="Card" Source="/SilverlightApplicatio
Post a Comment
Read more