Victor Stodell

Since we want to simplify administration by minimizing our server farm the subdomain that currently hosts our Team Foundation Server is going to be removed. This means that we will have to move the entire installation to the parent domain. Luckily we only have one server as application-tier and data-tier, and we are very few users, which makes the process a whole lot less dramatic. First of all we have to make sure that the new domain is ready to incorporate the server. It is not possible to perform any kind of user mapping, so all user accounts must have the same login name on the new domain as on the current domain. This also applies to the service accounts used by Team Foundation Server. The documentation around this procedure is well documented on  MSDN . The article describes the scenario to move from a workgroup to a domain, but the scenario from one domain to another works exactly the same. The entire process can be summarized in 5 steps: Ensure that all users hav...

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. Register server in Visual Studio Select active projects in Team Explorer 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\Softwa...

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