Update 7/19/2007: We have now published this guidance on MSDN as a TechNote. It is available for download from here: http://msdn2.microsoft.com/en-us/teamsystem/aa718845.aspx#TFS (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 http://support.microsoft.com/. 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.
Instructions:The guidance which was previously available from this blog entry is now available online at http://msdn2.microsoft.com/en-us/teamsystem/aa718845.aspx#TFS. 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 QuestionsQ: 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.
"What is a team project made up of?""Should all of my developers work on a single team project, or should I have many team projects representing every logical project our team is working on?""What are the tradeoffs of using too many team projects?""What is the relationship between team projects and Visual Studio solutions/projects?"
These are questions I get a LOT when people are planning their Team Foundation Server deployments. There have been assorted bits of information scattered throughout the documentation and blogosphere which can help to address these questions, but Doug Neumann (Senior Group Program Manager on the Team Foundation Server team) recently authored a whitepaper to bring all of this knowledge together. Check it out here.
Today I'm pleased to report that we have published a case study showcasing Clear Channel's adoption of Visual Studio Team System. The case study can be viewed here. I have been working with Clear Channel for several months now so it's exciting to be able to finally tell their story because it is truly representative of the paradigm shift which can be enabled by Visual Studio Team System.
After failing to implement Rational, Clear Channel was attracted to the team-oriented promise of Visual Studio Team System. By adopting Visual Studio Team System they moved from a low-morale development organization with frequent failures into an team made up of individuals who clearly understand their role in the development lifecycle, can more easily collaborate with their peers and other stakeholders, and who take ownership for the delivery of successful results.
If you are considering ways in which your team might benefit from Visual Studio Team System, or if you're already using the tools and simply looking for other ways you can put them to use, then I would encourage you to check out the case study.
We recently posted two new Channel 9 videos for your viewing pleasure.
As a reminder you can check out all of the Visual Studio Team System content on Channel 9 at http://channel9.msdn.com/tags/vsts. Or you can subscribe to the following RSS feeds: