Configuring Visual Studio 2005 Team Foundation Server with Windows SharePoint Services 3.0

Update 7/19/2007: We have now published this guidance on MSDN as a TechNote. It is available for download from here: (see TN1501 and TN1502). This update reflects minor formatting and wording edits based on feedback we received on the original blog post.

Update 6/12/2007: I have received several inquiries from people who are not sure how to obtain the HotFix mentioned in this guidance. In order to get the HotFix you must call Microsoft Support. You can find the phone number for Microsoft Support by visiting There is no cost to call Microsoft Support when requesting a known HotFix. Here's another important detail: when you request the HotFix you will need to do so by referencing KB #932544. Another important thing to note is that this KB article currently does not exist except in a "stub" format, meaning that if you or even the Support engineer searches the Microsoft KB article database you won't find a KB article by this number. But if they search the HotFix database for HotFixes which are linked to this KB article that's how they will locate the HotFix. Hopefully that clears up some confusion.

Update 4/26/2007: I wanted to point out that the WSS 3.0 MSF templates are available in English only. Functionally they should work if deployed to a non-English deployment of WSS 3.0, but obviously the template text will be in English. If you require localized templates you can wait for Team Foundation Server "Orcas", or if we have them available sooner than that then I will post them as an update here.

Now that Windows SharePoint Services 3.0 is available we have received several inquiries from people wanting to use WSS 3.0 with Visual Studio 2005 Team Foundation Server. While we have stated that the next version of Team Foundation Server 2008 will support WSS 3.0 out-of-the-box, some customers have understandably wanted a solution sooner than this. There are even a few posts in the community (most notably from Mike Glaser who did a lot of groundbreaking work here) who have demonstrated how to get WSS 3.0 working with Team Foundation Server. However, the problem we observed with the community guidance is that it can leave Team Foundation Server in a state which is not serviceable (see the Q&A below for more information on what this means). Therefore we have prepared the attached guidance to help users enable WSS 3.0 to work with Team Foundation Server in a manner which will remain serviceable.

The guidance which was previously available from this blog entry is now available online at TN1501 and TN1502 include the necessary instructions depending on where you wish to configure WSS 3.0.

Important: You will also need to contact Microsoft Support in order to obtain a HotFix to re-enable the Project Creation Wizard to work from Team Explorer after making these changes. We recommend that you obtain this HotFix prior to undertaking any of the steps in this documentation since it may take some time for you to get the HotFix. Detailed instructions on how to obtain this HotFix are provided in the documentation.

Frequently Asked Questions
When will Team Foundation Server support Windows SharePoint Services 3.0?
A: Microsoft is on track to deliver native out-of-the-box support for Windows SharePoint Services 3.0 in the next release of Team Foundation Server 2008. For customers with an immediate need, we have provided this interim documentation.

Q: I am trying to install Team Foundation Server 2005 onto a server that already has Windows SharePoint Services 3.0 installed. How can I get Windows SharePoint Services 2.0?
A: You will need to uninstall Windows SharePoint Services 3.0 and install Windows SharePoint Services 2.0 on port 80. You can then install Windows SharePoint Services 3.0 side-by-side as per the attached guidance, but you must ensure that Windows SharePoint Services 2.0 remains installed on the default port 80 in order for Team Foundation Server to remain serviceable.

Q: What does it mean to "remain serviceable"?
A: Serviceability refers to Microsoft's ability to provide maintenance releases (e.g. hotfixes, service packs), feature packs, and upgrades (e.g. to Team Foundation Server 2008). This can also impact your ability to run a Setup Repair. By following the attached guidance you can ensure that your Team Foundation Server deployment remains serviceable.

Q: I noticed that the guidance indicates that this solution is not officially supported. What does that mean?
A: We will provide support for this solution on a "best effort" basis. Due to the complexities involved with this solution, and the fact that this solution is meant to be an interim solution until we ship Team Foundation Server 2008, this guidance should only be used when WSS 3.0 support for Visual Studio 2005 Team Foundation Server is required. That said, if you run into problems, please let us know at the Team Foundation Server - Setup forum and we will do our best to help you.

-Brian Keller

Comments (30)
  1. I have some cutting edge (and bleeding edge) customers. They don’t necessarily enjoy playing the unsynchronized-product-release-cycle

  2. Anthony Borton says:

    Hi Brian,

    This is great news. I have a few customers that have been waiting for this for a while now.



  3. Just to catch you up, Microsoft’s Team Foundation Server v1.0 (released March 2006) only works with WSS

  4. TFS won’t support WSS 3.0 out of the box till the Oracas release, but a release candidate of how you…

  5. Lorsque l’on installe un serveur Team Foundation et que l’on créé des projets d’équipe, ceux-ci sont

  6. Luis Fraile says:

    Buenas noticias, ya se puede usar WSS 3.0 con TFS, Brian Keller , evangelista técnico de Team System,

  7. Vous l’aurez remarqué, les Team Project génèrent des portails Web basés sur WSS 2.0 (qui date de Windows

  8. Over the past several months we’ve gotten countless requests from people who want to use the new Sharepoint

  9. More and more customers are asking for WSS3.0 (SharePoint 2007) integration with Team System (TFS). As

  10. Archi says:

    It was officially announced that TFS V1 will not support WSS 3.0 awhile ago and I had my own post on…

  11. I try to avoid repeating the same news from the communities I am most closely aligned. I figure if I

  12. Buck Hodges says:

    Brian Keller has posted information on how to get WSS 3.0 to work with TFS 2005, which has been a very

  13. Mike's Blog says:

    Last Monday I read a post of Brian Keller about Configuring Visual Studio 2005 Team Foundation Server

  14. Amazing efforts by Mike Glaser and the VSTS Rangers (MCS consultants) have yielded results: a guide to

  15. MaD Blog says:

    Když byly uvolněny WSS 3.0 a MOSS 2007, bylo oznámeno že budou nekompatibliní se stávajícím Team Foundation

  16. Brian Keller 整理了一份 "How To" 將 TFS 的 Portal 掛載在 WSS V3 架構的白皮書. 目前他將該份白皮書 以 Blog 方式推出分享. 稱該份文件是 RC 狀態.

  17. Some of the common challenges which seem to be plaguing eeryone in the magical world of TFS: Best Practices

  18. If you’re a SharePoint user and haven’t tried out the new version ( WSS 3.0 ), you’re missing out. We

  19. В общем Аллилуя! Мы можем использовать WSS 3.0 с TFS 1.0 SP1! Для тех, кто не сравнивал WSS 3.0 с WSS

  20. Brian Keller explains how to integrate TFS with SharePoint Services 3.0 here . It’s a pre-release integration,

  21. Mike's Blog says:

    Since Brian Keller and Brian Harry requested me to test Configuring Visual Studio 2005 Team Foundation

  22. Оказывется, сделать это сложно, но можно. Brian Keller приводит подробное описание процедуры в своем

  23. Vorrei riportare alcune esperienze fatte con TFS in questi ultimi giorni perch

  24. Vous l’aurez remarqué, les Team Project génèrent des portails Web basés sur WSS 2.0 (qui date de Windows

  25. Vous l'aurez remarqué, les Team Project génèrent des portails Web basés sur WSS 2.0 (qui date de

  26. I have updated my older blog post to reflect the fact that the guidance for configuring Team Foundation

  27. I have updated my older blog post to reflect the fact that the guidance for configuring Team Foundation

Comments are closed.

Skip to main content