none
TFS 2008 to TFS 2010 Build scripts conversion

    Question

  • Hi,

    We are using tfs 2008 msbuild scripts on TFS 2010 using upgrade template. We are planning to migrate the builds to TFS 2010. Is there any tool which can help in conversion?

    Thanks in advance,

    LakshmiNarayan


    lakshmiNarayan

    Wednesday, May 16, 2012 6:27 AM

Answers

  • Hi Lakshmi,

    I am confused why you need to upgrade your msbuild scripts when you are already using Upgrade template. 

    As per my understanding (John, please correct me if I am wrong) 

    When upgrading from TFS 2008 to TFS 2010, all builds are “upgraded” in the sense that a build definition with the same name is created, and it uses the UpgradeTemplate  build process template to execute the build. This template basically just runs MSBuild on the existing TFSBuild.proj file.

    So, existing builds will run just fine after upgrade. But if you want to use the new workflow functionality in TFS 2010 Build, but still have a lot of MSBuild scripts that maybe call custom MSBuild tasks that you don’t have the time to rewrite? Then one option is to keep these MSBuild scrips and call them from a TFS 2010 Build workflow. This can be done using the MSBuild workflow activity that is avaiable in the toolbox in the Team Foundation Build Activities section.

    A walkthrough on how this can be done is available here, http://geekswithblogs.net/jakob/archive/2010/05/05/executing-legacy-msbuild-scripts-in-tfs-2010-build.aspx.

    There is nothing automated beyond this point because your custom tasks are your own and it is hard to build a generic tool to upgrade them.

    If you have any follow up questions feel free to get back to us.

    HTH
    Cheers, Tarun


    Please remember to mark the replies as answers if they help.

    Tarun Arora

    Blog: http://geekswithblogs.net/TarunArora  Subscribe in a reader

    Thursday, May 17, 2012 9:18 AM
  • Hi LakshmiNarayan,

    If you are planning to migrate your existing MSBuild scripts to Window Workflow, you can refer to Rangers Build Customization Guidance. It has some information on mapping most of the MSBuild extensibility targets with equivalent sequence in Window Workflow default build templates. 

    Saturday, May 19, 2012 5:22 AM

All replies

  • I think the only thing you need to change is what "MS Visual Studio 10.0/9.0/Common/.." path you are using.

    Upgraded template is good.

    Under Build Definition Edit configuration, Under "Process", under "Advanced", see if "MSBuild Platform" is "X86" or not.

    Make sure you are pointing to the correct TFS server..http://tfsserver...


    Arun Sangal Software Configuration Management Denver USA


    • Edited by Arun.Sangal Wednesday, May 16, 2012 6:43 PM
    Wednesday, May 16, 2012 6:42 PM
  • Hi LakshmiNarayan, 

    Thanks for your post.

    As Arun said, we can use the Upgrade template to build your existing TFSBuild.proj file.    

    For more information about upgrading TFS 2008 Build Definitions to TFS 2010, please refer to the Q/A in this blog: http://blogs.msdn.com/b/jimlamb/archive/2009/11/03/upgrading-tfs-2008-build-definitions-to-tfs-2010.aspx.   


    John Qiao [MSFT]
    MSDN Community Support | Feedback to us

    Thursday, May 17, 2012 2:17 AM
    Moderator
  • Thanks for your post.

    We are already using upgrade template.

    Now want to convert the scripts to TFS 2010, question is - any tools available which converts the ols scripts to new windows Work flow?


    lakshmiNarayan

    Thursday, May 17, 2012 3:35 AM
  • Hi LakshmiNarayan, 

    Thanks for your reply. 

    As far as I know, there’s no a convert tool which can convert the old script to workflow directly.    


    John Qiao [MSFT]
    MSDN Community Support | Feedback to us

    Thursday, May 17, 2012 6:10 AM
    Moderator
  • Hi Lakshmi,

    I am confused why you need to upgrade your msbuild scripts when you are already using Upgrade template. 

    As per my understanding (John, please correct me if I am wrong) 

    When upgrading from TFS 2008 to TFS 2010, all builds are “upgraded” in the sense that a build definition with the same name is created, and it uses the UpgradeTemplate  build process template to execute the build. This template basically just runs MSBuild on the existing TFSBuild.proj file.

    So, existing builds will run just fine after upgrade. But if you want to use the new workflow functionality in TFS 2010 Build, but still have a lot of MSBuild scripts that maybe call custom MSBuild tasks that you don’t have the time to rewrite? Then one option is to keep these MSBuild scrips and call them from a TFS 2010 Build workflow. This can be done using the MSBuild workflow activity that is avaiable in the toolbox in the Team Foundation Build Activities section.

    A walkthrough on how this can be done is available here, http://geekswithblogs.net/jakob/archive/2010/05/05/executing-legacy-msbuild-scripts-in-tfs-2010-build.aspx.

    There is nothing automated beyond this point because your custom tasks are your own and it is hard to build a generic tool to upgrade them.

    If you have any follow up questions feel free to get back to us.

    HTH
    Cheers, Tarun


    Please remember to mark the replies as answers if they help.

    Tarun Arora

    Blog: http://geekswithblogs.net/TarunArora  Subscribe in a reader

    Thursday, May 17, 2012 9:18 AM
  • Hi LakshmiNarayan,

    If you are planning to migrate your existing MSBuild scripts to Window Workflow, you can refer to Rangers Build Customization Guidance. It has some information on mapping most of the MSBuild extensibility targets with equivalent sequence in Window Workflow default build templates. 

    Saturday, May 19, 2012 5:22 AM