none
Getting around Excel Interop Assemblies for Office 2016? RRS feed

  • Question

  • I use a professional version of Visual Studio 2012.  I generally don't find a need to update my office software more often than every 6-12 years and in particular, due to Microsoft's antics with Windows 10 (the fiasco with forced upgrades, updates, and my absolute disgust with Cortana), lately, I am reluctant to upgrade ANY Microsoft software because they have lost my trust.

    However, I have written software for people in my company that they find useful and which makes use of .NET interop assemblies for Office and I have had reports that the software doesn't work with Excel 2016 which is what my company uses on their virtual desktops (I supply my own software so I don't currently use their virtual desktop).   The software imports records from a stock Excel 2010 spreadsheet and exports a robust, feature rich, compatible spreadsheet.  However, users with Office 2016 cannot use the software because of compatibility issues with the interop assemblies they have on their machine.  I need to know how I can make my software work with Excel 2016 interop assemblies (or force use of lower version assemblies) without purchasing the software myself.  Can I ship the necessary assemblies with my product?






    • Edited by primem0ver Wednesday, March 7, 2018 2:01 AM
    Wednesday, March 7, 2018 1:52 AM

All replies

  • Hi primem0ver,

    You need to install "Visual Studio 2010 Tools for Office Runtime" to run the same Office solution on multiple version of Office.

    Reference:

    Running Solutions in Different Versions of Microsoft Office

    Regards

    Deepak


    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, March 8, 2018 5:58 AM
    Moderator
  • Hi primem0ver,

    Is your issue is solved now?

    I find that you did not done any follow up after creating this thread.

    If your issue is fixed by you then I suggest you to post your solution and mark it as an answer.

    If your issue is still exist then try to refer the suggestions given by the community members.

    If you think that the suggestions given by the community member can solve your issue then mark the helpful suggestion as an answer.

    It will help us to close this thread and it also can be helpful to other community members who will meet with same kind of issues in future.

    If you have any further questions then you can let us know about it, We will try to provide you further suggestions to solve it.

    I suggest you to update the status of this thread and take appropriate actions to close it.

    Thanks for your understanding.

    Regards

    Deepak


    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.

    Tuesday, March 13, 2018 8:19 AM
    Moderator