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
Related
I had been scouring documentation to check how we can enable/show/display office add-ins in Outlook 2013. The button Get-Addins does not show in my Outlook 2013-32bit either. Here is a screenshot :
I tried enabling "connected experience" but I could not find the setting in Office 2013. Is there a configuration or registry key I need to set to be able to show my office add-ins in Outlook 2013?
Please note that these add-ins are successfully shown in the browser, in Office 2016 and 2019.
Thank you very much for any assistance you can extend to me.
Here is the version of Outlook 2013 (32-bit) I am working on :
Again, many thanks in advance.
Some application specific APIs only became available with Office 2016, per
https://learn.microsoft.com/en-us/office/dev/add-ins/develop/application-specific-api-model
and
https://learn.microsoft.com/en-us/office/dev/add-ins/reference/overview/excel-add-ins-reference-overview
However different aspects seems to be partially supported for Office 2013, per
https://learn.microsoft.com/en-us/office/dev/add-ins/reference/requirement-sets/office-add-in-requirement-sets
https://learn.microsoft.com/en-us/office/dev/add-ins/concepts/requirements-for-running-office-add-ins also seems to say 2013 is supported. So it depends on the exact API/functionality you are desiring...
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
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 wondering when i create my 365 mail app for outlook, will this work with Outlook 2010 and 2007? if so is there an obvious limitation?
Thankyou
No, Office Apps can work in Outlook 2013 and later versions. See Mail apps for Outlook for more information.
I have Outlook Addin Developed in visual Studio 2003. its using CommandBar for adding Addin Tab and menu for my Addin. it is working properly till Outlook 2010,but its not running in Outlook 2013, due to CommandBar issues.
I have debuged the Addin with outlook 2013.CommandBarControls not working in outlook 2013.
When my addin reach the following statement, outlook 2013 throws an exceptionatlcomcil.h - Debug Assertion Error.
SpCmdCtrl = spCmdBar-> FindControl(vMenuEmpty, vMenuID);
SpCmdCtrl is getting {0x00000000}.
I wonder why findControl() is not returning something.
The statement is working fine in Previous versions of Outlook.
Any Help is deeply Appreciated
Outlook 2013 doesn't allow you to work with commandbars.
See http://msdn.microsoft.com/en-us/library/office/jj229903.aspx
Regards,
Victor