Feedback by UserVoice


My feedback

  1. 80 votes
    Sign in
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    OfficeDev commented  · 

    This is a major problem. Microsoft wants developers to build what it ambiguously refers to as "Office add-ins" instead of VSTO (COM) add-ins going forward. This is why the Windows Store editions of Office do not support VSTO add-ins. Unfortunately, Microsoft has made it deceptively difficult to determine whether you have the click-to-run or Windows Store edition of Office installed (as of this writing), and not much easier to find the click-to-run edition in your O365 account.

    The bigger problem here, however, is that the Office.js API used to build "Office add-ins" is very basic and horrendously incomplete compared to .NET Framework / Office object model used to build sophisticated VSTO add-ins. Therefore, sophisticated VSTO add-ins used extensively in enterprise environments cannot simply be reengineered to "Office add-ins" that support only basic functionality. Unfortunately, professional Office users must continue to uninstall the lightweight Windows Store edition of Office that PCs now ship with and install the fully functional click-to-run edition that supports sophisticated add-ins.

    I don't disagree that transitioning from VSTO to Office.js is a good thing, but Microsoft's attempt at a transition has been premature and developers currently do not have the Microsoft tools they need to make the transition successful.

    OfficeDev supported this idea  · 

Feedback and Knowledge Base