Andrei Smolin

How Add-in Express supports Office 365 / Office 2019

This blog is about how these products support Office 2019 and Office 365:

  • Add-in Express for Office and .NET
  • Add-in Express for Office and VCL
  • Add-in Express Outlook Regions for VSTO
  • Security Manager for Outlook

You might already know that Office 365 and Office 2019 are, in fact, subsequent builds of Office 2016: in any Office 365 and Office 2019 application, the Application.Version property returns a string that starts with “16”.

This means Add-in Express products supporting Office 2016 also work in Office 365 and Office 2019. Though, there are several details to take notice of.

Office 2019 and Office 365

Microsoft uses “Office 2019″ for Office products that you buy as a one-time purchase, which means you pay a single, up-front cost to get Office apps for one computer. One-time purchases are available for both PCs and Macs. However, there are no upgrade options which means if you plan to upgrade to the next major release, you’ll have to buy it at full price (citation from support.office.com). As Office developers, you may run into a retail version of Office 2019 installed on the end-user’s machine and left non-updated. Be aware that that version may cause problems, so request the customer to update their Office version. The same applies to the initial retail version of Office 2016.

“Office 365″ represents the “software as service” approach: Office 365 applications are delivered and updated online via Click-to-Run. On this page at support.office.com they say that Office 365 is a subscription service.

Office 365 Insider (or Beta) channel

There are a few Office 365 update channels, each providing new builds at different update intervals. Different stability levels are assumed.

Insider is one of such update channels: it updates as often as 1-2 times a week. Every update is in fact a beta. To get a hand on the pulse, our testing team regularly run tests on the Beta channel builds.

Still, reacting to a change (once it is detected) may require some efforts from us and this will take some time. Also, Microsoft may introduce bugs with each update. And they did introduce bugs, quite rarely though. It also takes time for them to recognize the issue and fix it.

This means that Office 365 builds obtained through the Insider/Beta channel may not be supported immediately upon release. Using a non-tested beta build may break the add-in or even the add-in’s host application itself. We don’t recommend that your customers use the Insider channel.

Office from Microsoft Store

This is another flavor of Office. Because it works in a way that conflicts with per-user Office add-ins, only per-machine add-ins are supported. Find our research result in Office from Microsoft Store: a spreading source of issues. It looks like Microsoft has recognized the problem and we meet Office from Store on more and more rare occasions.

No support for Office Online, Office for Mac, Office for iOS

COM add-ins can only work on Windows Desktop. No other platform supports COM which is the base for Office on Windows. That is why, Add-in Express products do not support web versions of Office applications, also called Office Online. Nor do they support Office for Mac, iOS, etc.

For the avoidance of doubt, supported are only Office applications installed on Windows Desktop.

Security Manager for Outlook

Because Office 365 now updates regularly, you should update your Security Manager regularly, too. To get informed about new updates, subscribe to the Add-in Express RSS News Feed – please see this icon at the bottom of any page: Add-in Express RSS

Good luck!

6 Comments

  • https://secure.gravatar.com/avatar/1ed1010ea1b96106e70b119d452fda4c?s=32&d=https%3A%2F%2Fsecure.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D32&r=G Xavier N says:

    Hi Andrei,

    Read this blog post last month.
    https://devblogs.microsoft.com/dotnet/using-net-core-to-provide-power-query-for-excel-on-mac/

    With the introduction of .NET 5.0 and consolidation efforts of the different frameworks, porting to .NET Core (now just .NET 5.0) is not a question of when – it is just a question of how. I hope this post shed some light on the things you need to consider when choosing to port your Windows desktop app and make them cross platform.

    Not sure to understand all the in and out of the post but do you think it means com addins can be written in .net core and so be ported to macOs (and Linux) ? If so, will ADX think about a Addin Express version for .Net Core ?
    Regards. Xavier

  • https://secure.gravatar.com/avatar/29957f26ad2d8ba527fd9cc8cfa7b2e0?s=32&d=https%3A%2F%2Fsecure.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D32&r=G Andrei Smolin (Add-in Express Team) says:

    Hello Xavier,

    In a .NET Core Class Library project, Visual Studio disables the “Register for COM Interop” flag. This means such a library cannot be used as a COM add-in. Besides, COM add-ins are only available on Windows Desktop. So, it doesn’t look like there ever be a .NET Core version of Add-in Express add-ins.

  • https://secure.gravatar.com/avatar/feea36f7d08d69be9254132e55bda39b?s=32&d=https%3A%2F%2Fsecure.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D32&r=G Alex says:

    Hi Andrei,

    regarding these ongoing modenization efforts by Microsoft, are you planning to add support for the new WebView2 control (https://developer.microsoft.com/en-us/microsoft-365/blogs/announcing-webview2-for-office-add-ins-platform/) in the WebViewPane some time? Because currently the WebViewPane uses the old WebBrowser control, based on the Internet Explorer engine, if I looked correctly. Having an up-to-date browser engine in add ons would be really nice.

    Regards,
    Alex

  • https://secure.gravatar.com/avatar/ab4ec2858cfdf1e44dadf8c50fae314d?s=32&d=https%3A%2F%2Fsecure.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D32&r=G Dmitry Kostochko (Add-in Express Team) says:

    Hello Alex,

    I am afraid I do not quite understand your question. Microsoft is going to replace the web view control for Office Add-ins, i.e. for JScript add-ins. Add-in Express is a tool for creating COM Add-ins. We don’t use the System.Windows.Forms.WebBrowser control in our code. As for the WebViewPane advanced region – we use the WebViewOn and WebViewURL properties just for hiding the default content of an Outlook Folder. Then, we place your .NET form over that area.

    Is it what you were asking about? If not, please clarify your question.

  • https://secure.gravatar.com/avatar/feea36f7d08d69be9254132e55bda39b?s=32&d=https%3A%2F%2Fsecure.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D32&r=G Alex says:

    Hi Andrei,

    thanks for your clarification on this. I guess I’ve been too long out of outlook add in development and mixed up the WebViewPane with what’s rendered in our Form. I thought the webBrowser control was mandatory, but you’re right, its just a part of our form. I guess I took it from a random example back then.
    So thanks for bringing me on the right track again and sorry for taking your time ;-)

    Regards, Alex

  • https://secure.gravatar.com/avatar/29957f26ad2d8ba527fd9cc8cfa7b2e0?s=32&d=https%3A%2F%2Fsecure.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D32&r=G Andrei Smolin (Add-in Express Team) says:

    No problem at all!

Post a comment

Have any questions? Ask us right now!