Plunging into .NET Development

Weblog Pieter Gheysens
Microsoft .NET Development - C# - Enterprise Library - Visual Studio 2005 Team System - Compuware DevPartner - ...

Monday, May 19

VISUG TFS Session cancelled

I've cancelled my second Team Foundation Server session on Wednesday (first session was held on May 7, 2008) because I managed to corrupt my TFS 2008 installation while trying to upgrade to TFS 2008 SP1 (beta) last week-end. That means that my demo pc is currently out-of-order and without the prepared demos my session wouldn't be that interesting. I will try to reschedule the session to a later date and make sure that new features of TFS 2008 SP1 will be part of my presentation. A small consolation : I've uploaded my slides for download ...

Those who want to know more about the TFS 2008 SP1 beta failure can read my post in the MSDN forum.

Working with a Virtual PC (with Undo Disks enabled) would have prevented this issue, but I like to work on a dedicated main OS on my laptop for performance reasons and this is really the first time that I managed to bring the system down with upgrading to the latest bits. Bad timing!

All registered people - with a valid email address - for the VISUG session on Wednesday should have received a cancellation email.

Labels: ,

Friday, May 16

Hosting WCF service (.svc) in IIS

When hosting WCF services (.svc) in IIS on a client pc (XP Professional with IIS 5.1) I discovered that the .svc file in my browser wasn't showing me the usual service page with the link to the wsdl and example code how to call the service. I only got the markup text that was entered in the .svc file.

To get the WCF services running in IIS you need to map the .svc extension to the aspnet_isapi.dll on the IIS website. Apparently this was not automatically done after the installation of the .NET Framework 3.0. How to do this manually : go to your website in IIS > right click to get the properties for the website > tab Home Directory > button Configuration > Add mapping for .svc extension ...



Tuesday, May 13

Team System Quick Reference Posters

Today I stumbled upon a quick reference poster for the build process in Team Foundation Server, but apparently there are more interesting quick reference posters on Visual Studio Team System ...
  • Microsoft Team System Build Process
  • Microsoft Team System Licensing Overview
  • Light Weight Scrum Process Template for VSTS
  • Microsoft Team System Environments
Download here.


Thursday, May 8

#6 - delete vs destroy in TFS

Category : Administering Team Foundation Server Version Control

A delete operation in Team Foundation Server Version Control isn't a real delete. The item you've deleted is actually still there and kept in Version Control ...
  • I first created a new folder Pieter and checked in these changes

  • Then I deleted the folder and checked in these changes

  • At first sight, you might think that the folder is gone because you cannot see the folder anymore in Version Control.

  • Go to Tools > Options > Source Control > Visual Studio Team Foundation Server and check Show deleted items in the Source Control Explorer

  • Now you see that the folder is back, greyed out and marked with an x

In Team Foundation Server 2005 there's no option to destroy completely this folder. The information is kept forever in Version Control and you might even execute an undelete : right-click on the deleted folder and choose undelete!

In Team Foundation Server 2008 you now also have the option to destroy (a permanent delete action via the command-line) something forever - no undelete anymore possible afterwards. So, with TFS 2008, I tried it out and executed the command tf destroy $/VISUG/MainDev/Pieter ... but it returned me an error : the item does not exist on the server. Not true because I can still see it! What's happening?

The thing is that you need the deletion id of the item to force the destroy. How to get that deletion id? Request the properties of the appropriate item via the properties command. After that you will be able to pass the deletion id to the destroy command and the folder should be gone forever.