eScrum Update: ASP.NET AJAX Control Toolkit Version Conflicts

  • Article

For those who have experienced any problems getting eScrum (Now Available: Microsoft eScrum Version 1.0) installed and working due to ASP.NET AJAX Control Toolkit version conflicts:

Since you can't download previous versions of the ASP.NET AJAX Control Toolkit, and eScrum is compiled with a specific version, you may need to update the web.config file to allow automatic usage of a newer version of the ASP.NET AJAX Control Toolkit. eScrum has not been tested with newer versions, but may work well.

Add the following XML to the eScrum web.conifg file after the </configSections> close tag. Afterward, update the newVersion attribute to the version of the ASP.NET AJAX Control Toolkit that you are using.

<runtime>

      <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">

            <dependentAssembly>

                  <assemblyIdentity name="AjaxControlToolkit"

                        publicKeyToken="28f01b0e84b6d53e"

                        culture="neutral"/>

                  <bindingRedirect oldVersion="1.0.10301.0" newVersion="1.0.xxxxx.0"/>

            </dependentAssembly>

      </assemblyBinding>

</runtime>

Let me know if that helps/hinders.

1312

Comments

  • Anonymous
    June 15, 2007
    This week Microsoft released eScrum 1.0 - a combination package that includes a template for Visual Studio

  • Anonymous
    June 15, 2007
    PingBack from http://msdnrss.thecoderblogs.com/2007/06/15/microsoft-escrum-10/

  • Anonymous
    June 15, 2007
    Where is this template supported?  Through PSS?

  • Anonymous
    June 16, 2007
    More information here http://blogs.msdn.com/benchr/

  • Anonymous
    June 18, 2007
    Bil Simser on An attempt at working with eScrum. Martin Hinshelwood on TFS Event Handler: Prototype Released....

  • Anonymous
    June 18, 2007
    As advertised on a number of blogs, eScrum is a Web-based, end-to-end project management tool for Scrum

  • Anonymous
    June 28, 2007
    Rob, This is great. One question though, why not just ship the template with the Toolkit DLL's that it was compiled with? Wouldn't that reduce the pre-requisites and dependencies on the install? Thanks. Long story short, it would entail redistributing bits, which comes with its own set of pains