none
VSTO development for Office 2016 Preview RRS feed

  • Question

  • I have an application level addin for Word and would like to test it on Office 2016. I have build a Windows 10 VM (10130) and have installed the Visual Studio 2015 RC. I specified the office developer option in the VS installation.

    When I try to run my addin project from VS, I receive the following message:

    You cannot debug or run this projhect, because the required version of the Microsoft Office application is not installed.

    I am guessing this is beacuse the PIA that I am using is 15.0.0.0.

    Where can I get a copy of the PIAs for Office 2016, or failing that, are there any configuration changes that I need to make in order to develop for Office 2016 ?

    Thanks in advance for your help

    Friday, June 19, 2015 6:22 AM

Answers

  • I found this link which talks about modifying the project file to set the expected version of Office. This fixed the issue for me.
    • Marked as answer by PalerSash Monday, June 22, 2015 9:26 PM
    Monday, June 22, 2015 9:25 PM

All replies

  • Go to the COM references tab (in the Add Reference dialog window) and add a new reference to Word, the required PIAs will be generated automatically for you.

    Friday, June 19, 2015 7:09 AM
  • It doesn't help. Still see the same message:

    "You cannot debug or run this project, because the required version of the Microsoft Office application is not installed."

    The project builds and works correctly with 2016 Excel but I can't run and debug it by VS 2012.


    • Edited by RomanVD Saturday, June 20, 2015 4:28 PM
    Saturday, June 20, 2015 4:25 PM
  • In your previous message you mention a later version of Visual Studio, in your most recent reply you say " I can't run and debug it by VS 2012."

    No, you wouldn't be able to work with an Office 2016 VSTO project in VS 2012 because Office 2016 didn't exist when VS2012 was released...


    Cindy Meister, VSTO/Word MVP, my blog

    Saturday, June 20, 2015 6:24 PM
    Moderator
  • I found this link which talks about modifying the project file to set the expected version of Office. This fixed the issue for me.
    • Marked as answer by PalerSash Monday, June 22, 2015 9:26 PM
    Monday, June 22, 2015 9:25 PM