I am developing an Outlook add-in where I need to know what is the client release version like 2013, 2016, 2019, 365 etc.
While I can get client version using Office.context.mailbox.diagnostics.hostVersion but it returns version like 15.0.468.0.
I want to know is there any way to get versions like 2013, 2016 etc or is there any way to get that from client version 15.0.468.0?
For your scenario of using the client version to diagnose customer issues, I would recommended logging both the platform and the Outlook version.
Please use the Office.context.diagnostics.platform API to get the host platform. The version number can be retrieved from the Office.context.diagnostics.version API.
With the version number and platform (i.e. PC, Mac, or OfficeOnline) in hand, the Outlook release can be identified using the update history for each Outlook application. For example:
Outlook on Windows
Office 365 update history
Office 2016 and 2019 update history (C2R)
Office 2013 update history (C2R)
Outlook on Mac
Office for Mac (Office 365, 2019) update history
Office 2016 for Mac update history
Outlook on the web (on-premise)
Exchange Server update history (2013, 2016, and 2019)
Related
I would like to know how to efficiently debug a webb add-in (manifest.xml) add-in, and how to test it in anterior/past versions of Outlook (2013-2016).
More details : our team is struggling at debugging an outlook web add-in. It is published on the MS store.
Some of our customers are complaining about a weird behaviour (same for all), and I know they're using Outlook 2013 and 2016. Thing is, we can only test our add-in on our Office 365 developer E5 license and there, it works perfectly.
Thanks for the help!
You can see if this link helps you install the 2013 and 2016 clients.
https://support.microsoft.com/en-us/office/download-and-install-or-reinstall-office-2016-or-office-2013-7c695b06-6d1a-4917-809c-98ce43f86479?ui=en-us&rs=en-us&ad=us
I am developing Office addin for Outlook. Although I submitted my app to Office Store, the app was rejected because the behavior of my app was weird if users' Outlook version is 2013. Actually, fixing the problem to support Outlook 2013 is NOT reasonable, so I would like to submit my app to the store without supporting Outlook 2013. Is there any way to "unsupport" Outlook 2013?
You just need to change minimum support version
The documentation for onSend support in office add-ins states:
The on send feature is currently supported for Outlook on the web in
Office 365 (in preview), Exchange 2016 on-premises (Cumulative Update
6 or later), and Exchange 2019 on-premises (Cumulative Update 1 or
later). This feature is also available in preview on Windows and Mac
connected to an Office 365 subscription. Add-ins that use the on send
feature aren't allowed in AppSource.
I'm wondering if the onSend feature will support the following configuration:
Office 2016/2019 (not connected to 365) with Exchange 2016 on-premises.
Office 2016/2019 (not connected to 365) with Exchange via 365
Please find the image explaining availability of onSend on different platforms
I have already created an addin for Ms Outlook in Windows using visual studio 2010 and C#. It works fine with Ms Outlook 2007,2010,2013 and 2016 on Windows.
Now I would like to create the same addin for Outlook on Mac. I have downloaded a .pkg file of Outlook for Mac and have installed it. For activating It needs a Office 365 subscription and I have subscribed a one month free trial period.
Now to build the addin, I have surfed the internet.But I have not found any proper post related to this topic. Please help.
.NET/COM add-ins built with Visual Studio do not work on Outlook for Mac. Only the new web Outlook Add-ins (using JavaScript + HTML5 + CSS) will work. See: https://dev.office.com/docs/add-ins/overview/office-add-ins
Outlook for Mac does not support plug-ins as #Eric said. you could use office 365 apps(Office Add-ins ) or There are ways to add limited functionality to Outlook via AppleScript.
I am getting the following when trying to install the CRM 2015 plugin for Outlook:
I have Outlook 2010 32 bit version installed and I downloaded the 32 bit version of the CRM 2015 Outlook plugin.
thanks,
Stephen
This issue was caused by a duplication of ID's in the Sitemap as documented in this blog post:
UNABLE TO CONFIGURE OUTLOOK CLIENT AFTER UPGRADE TO CRM 2015
Did you have a chance to read first three sentences?
It looks like the add-in could connect to the CRM server. Try to contact your system administrator as the error message states.