TFS 11 Beta Power Tools on VS 12 RC (VS 11 RC ALM Demo image) – Process Template Editor not available in VS under Tools menu?!

Locked TFS 11 Beta Power Tools on VS 12 RC (VS 11 RC ALM Demo image) – Process Template Editor not available in VS under Tools menu?!

  • Tuesday, August 14, 2012 10:15 AM
     
     

    I have just installed the Visual Studio Team Foundation Server 11 Beta Power Tools on the Brian Keller's Visual Studio 12 RC ALM Demo image.

    I restarted the machine and opened VS.

    There is no Process Template Editor available in VS 12 under Tools menu.

    I can locate some of the other integration points from the Beta 11 power tools, for example:

    • Best Practices Analyzer
    • Team Collaboration page
    • Windows Shell Extensions

    I would appreciate any help/suggestion.

    Thank you,

    Ana 

All Replies

  • Wednesday, August 15, 2012 2:10 AM
    Moderator
     
     

    Hi Ana,

    Thank you for your post.

    After install TFS 2012 power tools, located under the Tools menu as Process Editor like following screen shot.

    Would you please show us the screenshot of Tools menu of your vs?

    Regards,


    Lily Wu [MSFT]
    MSDN Community Support | Feedback to us

  • Thursday, August 16, 2012 7:01 AM
     
     

    Hi Lily,

    this is the screenshot of my Tools menu after the installation.

    And here you can see other  integration points from the Beta 11 power tools package:

    Thank you,

    Ana


  • Friday, August 17, 2012 4:58 AM
     
     

    Hi Ana,

    What's the result of uninstall it, then re-install the power tools again?

  • Friday, August 17, 2012 10:42 AM
     
     

    I already tried running the setup again with the repair option (so I haven't uninstalled it and reinstalled it again), but it did not help.

    I now tried uninstalling and reinstalling the package again, but the Process Editor still does not appear in VS 12.

  • Friday, August 17, 2012 1:58 PM
     
     

    Hi,

    You mentioned "TFS 2012 power tools" - does that really mean TFS 11 Power Tools Beta or is there a TFS 2012 power tools and I'm not finding it?

    Thank you,

    Bill.

  • Friday, August 17, 2012 2:14 PM
     
     

    A Brian Harry states in his post - TFS Power Tools for the RC, they "won't be releasing a new build of the Power Tools with the Release Candidate.  The Beta Power Tools that are available will work with the RC build."

    I am using the Visual Studio Team Foundation Server 11 Beta Power Tools.

    Cheers,

    Ana


  • Friday, August 17, 2012 2:19 PM
     
     

    Ahh, I missed BHarry's post. Sorry about that, and thanks for the answer.

    I won't mark this as an answer because the original question was not mine  - I just tagged along with my own question...

  • Monday, August 20, 2012 8:40 AM
    Moderator
     
     

    Hi,

    I have the TFS 11 beta Power Tools installed on both VS 11BETA and VS 2012 RC, both work fine, the Process Editor feature installed.

    Would you check the %temp% folder for the log, file name like MSI9377F.TXT, you can share he log on Skydrive.  Also have a look at the event log, which source = MSIInstaller.

    This will help people diagnose the installation.

    thanks.


    Forrest Guo | MSDN Community Support | Feedback to manager

  • Tuesday, August 21, 2012 1:23 PM
     
     

    Hi Forrest,

    I cannot find any log regarding the installation of Power Tools in the %temp% folder. Could you be more precise about the log name/location?

    The Event Viewer (Windows Logs/Application) contains only informational messages regarding the installation of Power Tools (MSIInstaller), no errors.

    Thanx,

    Ana

  • Wednesday, August 22, 2012 3:26 AM
    Moderator
     
     

    The log is right under %temp%, named MSI9377F.txt. The postfix (9377F)may vary.  Do you find it?

    thanks.


    Forrest Guo | MSDN Community Support | Feedback to manager

  • Thursday, August 23, 2012 3:42 AM
    Moderator
     
     

    Process Editor is a TFS client side feature, power tool also has a set of server side features like Best Practice Analyzer. When you install the power tool, select customize install, do you see Process Editor feature?

    with regards,


    Forrest Guo | MSDN Community Support | Feedback to manager


  • Thursday, August 23, 2012 7:28 AM
     
     

    Hi Forrest,

    I'll answer to both your last questions.

    I cannot find any log file with that name on the snapshot where the tools are installed.

    So I started from a clean snapshot again, emptied all TEMP folders prior to installation, installed the power tools again ans still there is no such log file.

    The custom  installation shows that the Process Editor feature is selected for install.

    Thanx, Ana


  • Friday, August 24, 2012 2:29 PM
    Moderator
     
     

    It's abnormal that no msi logs over there. You may want to check the Windows Installer logging settings through group policy:

    "Computer Configuration" - >Administrative Templates -> Windows Components - > Windows Installer -> Turn off logging via package settings

    You should leave the setting unconfigured, or disabled.  Please check this setting and let me know if that's the reason it doesn't write log.

    thanks.


    Forrest Guo | MSDN Community Support | Feedback to manager

  • Thursday, August 30, 2012 11:51 AM
     
     

    Hi Forest,

    All settings in the group policy you mention are set on "Not configured". There is no setting with the exact name "Turn off logging via package settings", but I have following settings:

    • Logging
    • Disable logging via package settings
    • Disable Windows installer

    The virtual machine runs Windows Server 2008 R2 Standard SP1.

    Thanks,

    Ana

  • Friday, October 26, 2012 4:10 AM
     
     

    I have the same exact issue with the VSTFS 2012 power tools downloaded from here: http://visualstudiogallery.msdn.microsoft.com/b1ef7eb2-e084-4cb8-9bc7-06c3bad9148f/view/Discussions/2

    Is there a fix for this?

    Thanks,

    D2F

  • Friday, October 26, 2012 4:00 PM
     
     
    Are you using the Express version of Visual Studio?

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