locked
Adding 2010 Power Tools to VS Premium

    General discussion

  • We are using the comments check-in policy that is included in the power tools.  Since that means all users must have the power tools installed, we didn't like the fact that we had to depend on the users to get the power tools installed separately.  For VS 2005 and 2008 we had a script to install Team Explorer and includes the power tools.  That doesn't work for VS premium since it comes with TE installed and they can connect right out of the box.  So for my solution I wanted to try to integrate the power tools install directly into the VS premium install before are developers started installing it.  It seems to have been a success. 

    I made a blog post about what it takes to do it.  http://stanleydevo.blogspot.com/2010/04/adding-2010-power-tools-to-vs-premium.html

    Blog Post---

    With Team Explorer being included in the Visual Studio Premium and Ultimate install, you may wish that the TFS Power Tools are also included. Well they can be. You must modify four files located in the VS disk Setup folder but it can be done. Start by backing up the LocData.ini, vs_setup.pdi, baseline.dat, and setup.sdb files. Following these instructions will add the power tool directly into the install.

     


    setup\LocData.ini

    Add the bold lines below:
    [gencomp89,{12CDA52C-7A8F-4785-8A22-53C87393FEE0}]
    ComponentName=Microsoft Help Viewer 1.0 x64
    [gencomp459,{12CDA52C-7A8F-4785-8A22-53C87393FEE0}]
    ComponentName=Microsoft Team Foundation Server 2010 Power Tools


    [VS Custom]
    ProdDesc=Microsoft Visual Studio 2010 Premium


    setup\vs_setup.pdi
    In the [Complete Component List] add
    GFN_TFS Power Tools

    In the [Complete Dependency List] and [Microsoft Visual Studio 2010 Premium - ENU] list add
    gencomp459,{12CDA52C-7A8F-4785-8A22-53C87393FEE0}


    setup\baseline.dat
    In the [Complete Component List] add
    GFN_TFS Power Tools

    At the end, just before [VS Custom] add the following. You may want to change the value in the “CommandLine”
    setting. This will set which power tool features are installed.

    [gencomp459,{12CDA52C-7A8F-4785-8A22-53C87393FEE0}]
    BlockorWarn=0
    CleanCost=50000
    CommandLine=ADDLOCAL=TFPS,CLI,VSIP,CHECKINPOLICIES
    ComponentType=3
    EncryptionOpt=0
    EstInstallTime=180
    GFN=GFN_TFS Power Tools
    HiddenFeature=0
    IgnoreLaterVersions=0
    InstallBeforeVS=0
    InstallOnAMD64=1
    InstallOnFutureNT=1
    InstallOnIA64=0
    InstallOnLHS=1
    InstallOnNetServer=1
    InstallOnVista=1
    InstallOnWinXP=1
    InstallOnWin7=1
    InstallOnWin7Server=1
    InstallOnx86=1
    InstallPackage=tfsPowerTools2010.msi
    LogFile=dd_tfsPowerTools2010_enu.txt
    Repair=1
    Uninstall=1
    Reboot=0
    RebootLaterOk=1
    ReturnType=NetRtReturnCheck
    moduleid=3E0AC23F-5A84-45FF-B03D-6803907C46C5
    ProductCode={B6DC31D8-A303-4D14-9C88-59F183F55BEC}
    UpgradeCode={61C7C09D-87AE-466C-9C2D-107F49465429}
    version string=3.0.30423.0
    VersionCheck=MSIVersionStringCheck
    DDownloadFile=tfsPowerTools2010.msi

    setup\setup.sdb

    At the end of the [GUID to Friendly Name Mapping] list add:
    3E0AC23F-5A84-45FF-B03D-6803907C46C5,GFN_TFS Power Tools

    At the end of the [CompleteComponentList] list add:
    gencomp459,{12CDA52C-7A8F-4785-8A22-53C87393FEE0}

    At the end of the [PreInstallOrder] list add:
    GFN_TFS Power Tools

    At the end of the [InstallOrder] list add:
    GFN_TFS Power Tools

    At the end of the [PostInstallOrder] list add:
    GFN_TFS Power Tools

    At the end of the [CD Info] list add:
    GFN_TFS Power Tools,1,wcu\TFPT,installdisk1

    At the end of the [Component Order] list add:
    1,GFN_TFS Power Tools

    Copy MSI to VS Install Source

    Now in the WCU directory of your install source directory (ie. en_visual_studio_2010_premium_x86_dvd_509357\WCU) create a TFPT folder. Copy the 2010 power tools to this directory and rename it tfsPowerTools2010.msi.
    Friday, April 30, 2010 3:28 PM

All replies

  • I just discovered that these instructions work exactly the same for merging the Power Tools install into the Team Explorer install.  Except for the fact that there is no Setup folder.
    Friday, April 30, 2010 6:14 PM
  • Any reason why these wouldn't work against VS 2010 Professional?
    Friday, April 20, 2012 2:39 PM
  • Nope, this would work for Pro as well, just some small changes may be needed.

    Edit: Now that I think about it, I don't think Pro has Team Explorer integrated.  Which is why I think I wrapped power tools into the TE install.

    Friday, April 20, 2012 2:43 PM
  • I checked and VS 2010 Pro does have Team Explorer packaged with it.  Also versions of VS 2010 (except Express) have Team Explorer included.

    http://www.edsquared.com/2010/04/13/Team+Explorer+Included+In+Visual+Studio+2010+Installation.aspx

    I tested this morning and the above directions do work for Visual Studio 2010 Professional as well.

    Thanks David!

    Friday, April 20, 2012 5:10 PM