none
Best approach to develop a MS Word plugin that supports from MS Office Word 2007 to 2016 RRS feed

  • Question

  • We need to develop a MS Office Word plugin that must be compatible with office 2007 to all the way up current version. The plugin will be delivered with a desktop app that we are developing using Electron. We want a single code base for the plugin that supports all the versions of MS office. What will be the best approach for us? Plugins that are developed in Office JavaScript API - are they compatible with older versions of MS Office (eg. Office 2007) or should we go for C# or any other alternative?



    • Edited by Anik WS Wednesday, June 20, 2018 6:16 AM
    Wednesday, June 20, 2018 6:14 AM

All replies

  • Hello Anik,

    Office Apps were introduced with Office 2013. They can't be run in earlier Office versions

    Looks like you need to develop a COM add-in, for example, you can use VSTO for that. You need to choose an older Office add-in template for targeting Office 2007 or simply use interop assemblies that correspond to the lowest Office version (Office 2007). See Run Office solutions created by using Visual Studio 2010 and above for more information. 

    Also you may take a look at Add-in Express. They allow to develop a version-neutral COM add-ins out of the box. 


    profile for Eugene Astafiev at Stack Overflow, Q&A for professional and enthusiast programmers

    Wednesday, June 20, 2018 8:35 AM
  • Hello Anik WS,

    According to the top stick thread on the forum, Post Word Add-ins questions to StackOverflow.  , I would suggest you post your issue related to Office JavaScript API to StackOverflow. For current thread, I will move it to Off-Topic forum.

    Thanks for understanding,

    Best Regards,

    Terry


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Thursday, June 21, 2018 6:14 AM