How Microsoft uses Team Foundation Server internally

A good read:

About the technical side:

Update Warning: Security Update for SQL Server 2005 Service Pack 2 (KB948109) might break Reporting Services

Name des Updates und Nummer:


  • Security Update for SQL Server 2005 Service Pack 2 (KB948109)
    version 9.00.3068.00 released on 7/8/2008

Applies to:


  • SQL Server 2005 Service Pack 2 with Reporting Services installed

Symptoms & Result:


  • After installation the SQL Server 2005 Reporting Services service might not start. Therefore the Reporting Services cannot be used anymore.

Distribution:


  • The Update is distributed via Windows Update.

Workaround:


  • Uninstall the update (requires a restart).

My recommendation:
(for your internal SQL server you use for TFS)


  • Do not install the update and wait for the next service pack release.

Related Links:


Visual Studio 2008, .NET 3.5 and TFS 2008 Service Pack 1 released

Service Packs for VSTS/TFS do not only contain bug fixes, but quite a few nice new features as you can read here (more general) and here (TFS-specific).

Download links:

If you have trouble installing SP1 look here and here.

 

Tip #1: Uninstall Visual Studio Hotfixes first

If you previously installed a Visual Studio 2008 Hotfix, you must run the Hotfix Cleanup Utility before installing Visual Studio 2008 SP1. For more information, see Visual Studio 2008 Hotfix Cleanup Utility for Installing Visual Studio 2008 SP1.

RemoveHotfixesFirst

 

Tip #2: Have enough disk space available on your primary hard drive:

RequiredFreeSpace 

You can read here why.

 

Tip #3: If you have Team Explorer or TSWA on your TFS you need to install… (Thanks to Hakan Eskici)

… Visual Studio 2008 Service Pack 1 and  TFS 2008 Service Pack 1 (in that order!).

 

Tip #4: Integrate installation of TFS and SP1 (“Slipstream”)

The steps to produce a so-called “slipstream” installation package are documented in the TFS Installation Guide in the chapter “How to: Integrate the Installation of Team Foundation Server and Service Pack 1“.

There are a few reasons why you must do that (e.g. upgrading to SQL Server 2008) you can read in Brian Harry’s blog post.

Slipstream_Step2 Slipstream_Step3 Slipstream_Step4 Slipstream_Step5

 

Tip #5: Ignore Windows Update reboot prompt (Thanks to Brian Harry)

If you get a Windows Update prompt to reboot during SP1 installation, ignore it (don’t reboot).  Wait until after the SP1 installation completes and then reboot.

 

Tip #6: Uninstall and reinstall Team System for Database Development GDR (Thanks to Brian Harry)

If you have a prerelease of the Team System for Database Development GDR (that supports SQL 2008) installed, you will need to reinstall it after upgrading to SP1.

 

Screenshots from applying TFS 2008 SP1:

TFS2008SP1_Step1 TFS2008SP1_Step2 TFS2008SP1_Step3 

 

Screenshots from applying VS 2008 SP1 (online installer) on at TFS with only Team Explorer installed:

VS2008SP1_Step1 VS2008SP1_Step2 VS2008SP1_Step3 VS2008SP1_Step4

Using images in description fields

Requires:

  • The use of HTML description fields in stead of the default description field.
  • Team System Web Access (TSWA) to insert the pictures.

 

Steps:

  1. Use a HTML fields for your descriptions instead of plan text fields
    (might need to copy the old descriptions programmatically).
  2. Add the image you want to use to the work item’s attachments:

    Step1_AddAsAttachement
  3. Save the Work Item.
  4. Double-click your attachment. IE opens. Copy the URL to the attachment to the clipboard.

    Step3_CopyUrl
     
  5. Open the Work Item in Team System Web Access and use the “Insert Images” bottom (from the toolbar within the HTML field):

    Step4_TSWAClickInsertImages
  6. Paste the attachment-URL from clipboard:

    Step5_EnterURL
  7. Save the Work Item.
  8. Done. You can see your picture in the HTML description field.

    TSWA:
    Step6_YouSeeThePicture

    Team Explorer:
    Step8_Voila

Users can see all team projects after upgrading from TFS 2005 to 2008

  1. Make sure all team project members are added to the appropriate groups (Project Administrators, Contributors and Readers).
  2. For every team project remove the “[Server]\Team Foundation Valid Users” group from the team project settings (Team Project Settings ยป Securty).

    RemoveValidUsers
  3. Done. Regular members now should only see team projects where they have permissions.

 

Enjoy!

Version Control Tip: Excluding specific files from multiple checkout

Question:

Can I define a file name, not only a file type (extension), if multiple checkout is allowed for the whole Team Foundation Server?

Answer:

Yes, that is possible, although the UI shows “file extensions” and displays it in a way that you might think that it’s not supported.

As a result you can specify that *.cs files in general do support multiple checkout but a certain file called “specific.cs” follows exclusive-checkout logic.

FileTypes2

 

Enjoy!

-Neno