none
What are the new API's for Office 2016 COM libraries, compared to Office 2013? RRS feed

  • Question

  • Hi,

    I'm doing some application development that requires Office 2013 and Office 2016 support.  Because my Visual Studio 2015 project library references will be pointing to the "16.0" COM Object Libraries provided by Office 2016, any new features that I develop need to utilize only the APIs that are backwards compatible with 2013.  Is there any documentation that lists what are the new Office 2016 APIs?  It would be nice to know these differences so that I can maintain backwards compatibility for now, and also to learn what the new 2016 capabilities are.

    Thanks,

    Tam Bui

    Friday, June 17, 2016 12:28 AM

Answers

  • Hi Tam Bui,

    According to your description, are your developing VSTO add-in project? if so, if you create a solution using a project template for Microsoft Office 2016, the solution will run in the 2013 Microsoft Office system only if it does not use features that are new in Microsoft Office 2016".

    In addition you could refer to VBA improvements in Office 2016

    For more information, click here to refer about Running Solutions in Different Versions of Microsoft Office

    • Proposed as answer by David_JunFeng Sunday, June 26, 2016 2:57 PM
    • Marked as answer by David_JunFeng Monday, June 27, 2016 9:46 AM
    Monday, June 20, 2016 5:45 AM

All replies

  • @Tam,

    I'm afraid the official VBA documentation (https://github.com/OfficeDev/VBA-content) doesn't list what's new in COM on Office 2016.

    However, I bet that most VBA development done today is compatible backwards until Office 2007, unless you use really, really new object members.

    For example: I develop Excel Applications in VBA and my most recent applications (with over 100+ modules) are backwards compatible with Office 2007, 2010 and 2013.

    Is there something specific that concerns you?


    http://www.ambienteoffice.com.br - http://www.clarian.com.br

    • Proposed as answer by David_JunFeng Sunday, June 26, 2016 2:57 PM
    • Marked as answer by David_JunFeng Monday, June 27, 2016 9:45 AM
    • Unmarked as answer by Tam Bui Friday, July 1, 2016 11:31 PM
    Monday, June 20, 2016 12:49 AM
  • Hi Tam Bui,

    According to your description, are your developing VSTO add-in project? if so, if you create a solution using a project template for Microsoft Office 2016, the solution will run in the 2013 Microsoft Office system only if it does not use features that are new in Microsoft Office 2016".

    In addition you could refer to VBA improvements in Office 2016

    For more information, click here to refer about Running Solutions in Different Versions of Microsoft Office

    • Proposed as answer by David_JunFeng Sunday, June 26, 2016 2:57 PM
    • Marked as answer by David_JunFeng Monday, June 27, 2016 9:46 AM
    Monday, June 20, 2016 5:45 AM
  • Great link, David, I didn't know that.

    http://www.ambienteoffice.com.br - http://www.clarian.com.br

    Monday, June 20, 2016 11:23 AM
  • David,

    I am doing two types of development:  One where I have a WPF desktop application that uses the Office COM libraries for OneNote, Outlook, and PowerPoint.  And I have another project where I am developing a VSTO add-in for Outlook.

    Thank you for the link to the VBA improvements in Office 2016.  This gives me an idea of what to look for.

    Regards,

    Tam

    Friday, July 1, 2016 11:30 PM