I know that Outlook 2013 and 2016 disable add ins if start time is more than 1 second. Does Outlook 2010 have the same functionality?
Nope. The performance criteria for keeping add-ins enabled was introduced with Outlook 2013. See New in Outlook for developers for more information.
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 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
Visual studio suggest to create different VSTO project for outlook 2010 and outlook 2013 like a picture. However my Addin for outlook 2010 also works and for 2013. Any body know about different in these approaches?
The difference is that Outlook 2010 interops will be used in the project. So, IntelliSense will not show you methods and properties introduced in latest (Outlook 2013) versions.
See Running Solutions in Different Versions of Microsoft Office for more information.
I have developed word addin 2010 using visual studio 2012. I have created setup file using below MSDN link.
http://msdn.microsoft.com/en-us/library/cc442767.aspx
When i run this for ofice 2010 or office 2013 it works fine but it doesn't work for office 2007.
I though it would be word addin issue so I have created word addin 2007 and still have issue.
Can somebody suggest what can be the issue?
Add-in functionality changed again between Office 2007 and 2010, to support new features like the changed UI (RibbonBar). The addin you created for Office 2010 uses features that did not exist in the Office 2007 apps (Word/Excel etc).
Office Add-ins are typically forward compatible only. That is future version of Office support older older plugins, but the opposite is simply not possible as new features get added all the time.
e.g.
Write an Office 2007 addin and it will likely work on Office 2007, Office 2010 and Office 2013.
Write an Office 2010 addin and it will likely work on Office 2010 and Office 2013.
Write an Office 2013 addin and it will likely only work on Office 2013.
Please note that while they "work" they will often look very old-fashioned as they typically use the older UI elements and not the latest version.
Create a 2007 add-in instead
If you really need Office 2007 support, you need to create a 2007 Add-in instead (as well?). Otherwise you will likely be using features that simply do not exist in Office 2007. The only possible (unlikely) alternative is to add Office 2010 DLLs to the machines, but as you are then effectively upgrading Office I doubt that is legal without a Office 2010 licence (so you might as well upgrade them anyway).
Try to attach to the project the Interop.Word dll of Word 2007.
Also exchange the Office Object Library dll 12- which comes along with Word 2007.
Hope this helps.
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