Microsoft hasn't released an updated version of the eScrum process template for Visual Studio Team Foundation Server (TFS) 2008 Beta 2, code name "Orcas."  Until a supported version is available, these instructions will enable you to deploy the eScrum 1.0 process template (for TFS 2005) on TFS 2008 Beta 2.

Assuming you already have TFS 2008 Beta 2 up and running, you will need to install the following prerequisites:

1. Microsoft Anti-Cross Site Scripting Library v 1.0
2. Microsoft ASP.NET 2.0 AJAX Extensions 1.0
3. Visual Studio 2005 Team Explorer (the eScrum installer checks for it).  If you are adventurous, you could modify the eScrum msi file using Orca (not to be confused with Orcas) to eliminate the launch condition check for Team Explorer 2005.  Orca is a msi editor packaged in the Windows SDK, but you can download it separately here.

Once you have the prerequisites, install the eScrum template.  In addition to adding a process template to TFS, the installer will also deploy a WSS 2.0 site template and create an additional website.  After the installation you will modify the website configuration and replace the WSS 2.0 site template with a WSS 3.0 site template.

Follow these steps to remove and replace the eScrum WSS 2.0 template that was installed in WSS 3.0. 

1. Download the eScrum WSS 3.0 template and place it in a temporary directory on the TFS server (c:\temp).  I upgraded this template to WSS 3.0 by installing it on a WSS 2.0 image and then performing an in-place upgrade to WSS 3.0.
2. Remove the WSS 2.0 template that the eScrum installer deployed.  Run the following command on the TFS server (or the WSS server if you split WSS from TFS): C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN\stsadm -o deletetemplate -title eScrum
3. Reset IIS 
4. Deploy the template you downloaded by running the following command: C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN\STSADM.EXE -o addtemplate -filename "c:\temp\escrum.stp" -title eScrum
5. Reset IIS

Follow these steps to ensure the eScrum website is configured properly (there is a website on the TFS server in addition to the WSS site).

1. Open the eScrum web.config file (C:\Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Web Services\eScrum\) and ensure the following configuration section is the first node in the <configuraiton> section:

  <configSections>
        <sectionGroup name="system.web.extensions" type="System.Web.Configuration.SystemWebExtensionsSectionGroup, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35">
            <sectionGroup name="scripting" type="System.Web.Configuration.ScriptingSectionGroup, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35">
                <section name="scriptResourceHandler" type="System.Web.Configuration.ScriptingScriptResourceHandlerSection, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="false"/>
                <sectionGroup name="webServices" type="System.Web.Configuration.ScriptingWebServicesSectionGroup, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35">
                    <section name="jsonSerialization" type="System.Web.Configuration.ScriptingJsonSerializationSection, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="false"/>
                    <section name="profileService" type="System.Web.Configuration.ScriptingProfileServiceSection, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="false"/>
                    <section name="authenticationService" type="System.Web.Configuration.ScriptingAuthenticationServiceSection, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="false"/>
                </sectionGroup>
            </sectionGroup>
        </sectionGroup>
        <section name="loggingConfiguration" type="Microsoft.Practices.EnterpriseLibrary.Logging.Configuration.LoggingSettings, Microsoft.Practices.EnterpriseLibrary.Logging, Version=2.0.0.0, Culture=neutral, PublicKeyToken=1a5b963c6f0fbeab"/>
    </configSections>

1. Using Visual Studio 2008 Beta 2 Team Explorer, create a new team project using the eScrum template. 
2. Once the project is created, there is one more configuration step required to get the eScrum website to work.  Edit the RegisteredGroups xml file located in C:\Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Web Services\eScrum\RegisteredGroups.xml and add the name of your TFS server and Project (you can add more projects by adding more <Server> nodes), for example:

<?xml version="1.0"?>
<RegisteredGroups xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <isflatGroupCollectionDirty>false</isflatGroupCollectionDirty>
    <Server Name="TFSSETUP" Uri="http://orcasbeta2_tfsvsts:8080/">
        <Group Name="eScrumProject" />
    </Server >
</RegisteredGroups>

Verify the eScrum website is working by accessing the url where you installed it.

Verify the eScrum WSS 3.0 site is working for the TFS project you created.

Although unsupported, I hope these instructions will help until Microsoft releases a Visual Studio 2008 TFS eScrum process template.

---

Posted 09-29-2007 8:48 AM by John Powell, PMP, MCPD, MCSD