Dmitry Kostochko

Support for Office 2013 and Visual Studio 2012 coming soon

For the last few days we have received quite a lot of questions with one prevailing theme – When are you going to add support for Office 2013? The first one arrived a few hours after Microsoft had published Office 2013 CP and put a smile on our faces: Office 2013 has been out for a few hours and there is no update yet? ;)

As you may guess, we have started research immediately and now I can officially announce:

The Add-in Express for Office product line, i.e. Add-in Express for Office and .net and Add-in Express for Office and VCL, will have added support for Office 2013 Customer Preview by August 31. Add-in Express for Office and .net will also fully support Visual Studio 2012.

Support for Visual Studio 2012

There is not much to say about this since Visual Studio 2012 has very few changes related to the good old Office COM add-in development. We will simply support the most recent version, period.

Support for Office 2013 Consumer Preview

It’s too early to speak of improvements or new features either, though there are 2 things I can state with certainty:

  • All Office 2013 applications will be supported including Outlook, Excel, Word, PowerPoint, Access, Publisher, InfoPath, Project and Visio.
  • As usually, the new versions will be backward compatible with older versions of Add-in Express. We are trying to minimize your work and enable you to support the new version of Office 2013 by simply rebuilding your current code.

If you have any questions, comments or suggestions, it is the right time to let us know.


  • Pierpaolo says:

    In addition to the the compatibility with VS 2012 and Office 2013, are you planning to integrate also the new HTML 5.0 and java script model object to crate agaves?

    Does this make sense at all?


  • Dmitry Kostochko (Add-in Express Team) says:


    Thank you for this very good and topical question!

    We are on the design stage now. Unluckily, we have run into so many limitations that do not let us make the platform more or less universal. The Common Office API limits the developer in many ways compared to the Office Object Model. Moreover, it is oriented to asynchronous work, which creates additional complexities when working with large bulks of data.

    So, at the moment I cannot give any definite answer to your question.

Post a comment

Have any questions? Ask us right now!