VSTO Runtime Installation Checks with Click-To-Run installations


  • Our products utilize the VSTO Runtime v4.0 to run, and during our installations we check to see if the VSTO4 Runtime is installed.  Currently we do this by checking if the registry keys for the v4 runtime exist... see this response here:

    This has worked in all cases until we started seeing clients that are using the new "Click To Run" experience (including nearly everyone at Microsoft now).  You can also get this with the Free Office preview.

    Anyway, on these machines, the v4R subkey does not exist under the VSTO Runtime Setup key.  There are instead the v4 and v4M keys (with subvalues, but not all that exist on a normal machine with the v4R key).  When we run our installer on these machines, it obviously fails because it thinks there is no Runtime on the machine.  However, if we directly install the application (bypassing the pre-req checks), we properly run.

    The VSTO files are properly placed in the Program Files\Common Files\Microsoft Shared\VSTO\10.0 folder, however, they are not the latest version (they are version 10.0.31125.0 which is the version before the release in October last year).

    So my questions are really the following:

    1. How should we be properly checking for the VSTO Runtime on the machine between regular installs and Click-To-Run installations?

    2. Why is the version that is downloaded as part of Click-To-Run (on demand) not the latest version of VSTO?  This could have a problem for us as we depend on some of the fixes in the latest release.

    ~Joe | Enriching TFS through Office integration

    • Edited by Joseph Buys (TS) Monday, January 14, 2013 10:52 PM inserting hyperlink
    Monday, January 14, 2013 10:51 PM

All replies

  • Hi Joe,

    Thanks for posting in the MSDN Forum.

    I will involve some experts into your thread to see whether they can help your out. There might be some time delay, appreciate for your patience.

    Have a good day,


    Tom Xu [MSFT]
    MSDN Community Support | Feedback to us
    Develop and promote your apps in Windows Store
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Wednesday, January 16, 2013 5:37 AM
  • You can have multiple conditions using OR operator in your launch conditions

    in your Registry Search you need to have 3 launch condition properties for v4, v4R, v4M

    then on the launch condition verifier you set the Condition Field to

    v4>=<value> OR v4R>=<value> OR v4M>=<value>

    Wednesday, January 16, 2013 5:57 AM
  • I had already considered this option, however, I didn't think this was a "good" way of verifying.  The reason is that on many systems, you get these other reg keys, even when VSTO Runtime is not installed.  So it wouldn't be a "safe" check.

    ~Joe | Enriching TFS through Office integration

    Tuesday, January 22, 2013 11:22 PM
  • Dear Customer,

    Your question falls into the paid support category which requires a more in-depth level of support.  Please visit the below link to see the various paid support options that are available to better meet your needs :;en-us;offerprophone



    Wednesday, February 20, 2013 12:46 AM