Is there any way in which I can target Outlook 2016 and Outlook 2019 separately? I want to apply certain styles for Outlook 2019 only, and not for Outlook 2016.
You can use conditional logic like the following one:
Outlook 2013 <!--[if mso 15]> your code <![endif]-->
Outlook 2016 <!--[if mso 16]> your code <![endif]-->
Read more about that in the Outlook conditional CSS article.
Not easily. Outlook 2019 version is still 16.x.x.x. It is essentially Outlook 2016 forked from 2016 in early 2019. Office 365 versions of Outlook are actually newer than 2019.
Why exactly do you need to do that?
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
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.
We need to develop add-in for the Office 2016. We are using the Visual studio 2013. It is only showing the Office 2013 add-in templates. Is it possible to create Office 2016 add-in from Visual studio 2013? If so, kindly let me know the steps.
You need VS 2015 to get the specific templates for Office 2016. VSTO only ever provides templates for "current" versions of Office.
If Office 2013 is installed you can develop an Add-in for it. There should be no problem installing and running it in Office 2016 - unless you want to use technology specific to 2016. In that case, you could use late-binding (PInvoke) for the 2016-specific portions, but debugging/testing would be a bit of a pain.
You can download the free Visual Studio 2015 Community edition (https://www.visualstudio.com/en-us/downloads/download-visual-studio-vs.aspx) as well as the VSTO package (https://www.visualstudio.com/en-us/features/office-tools-vs.aspx): VSTO does integrate into the Community edition for version 2015 (and 2013, for that matter). Licensing restrictions would apply, of course.
Other than that, you'd need to upgrade to a full VS 2015.
You can develop and run Office 2016 addins in VS2013. No need to upgrade to VS2015.
Install VSTO 4.0 extension for VS2013
Create Office 2013 plugin using Visual Studio template
Open project file and replace office version string "15.0" to "16.0" in ProjectExtensions section. Look for this of similar string to edit:
OfficeVersion="15.0" VstxVersion="4.0" ApplicationType="Outlook" Language="cs" TemplatesPath="" DebugInfoExeName="#Software\Microsoft\Office\15.0\Outlook\InstallRoot\Path#outlook.exe"
Yes, it is possible. The add-in created in Visual Studio 2013 can be run in Office 2016. You can read more about that in the Running Solutions in Different Versions of Microsoft Office article.
In case if you need to use new methods and properties available only in Office 2016 you can use the Reflection mechanism (see Type.InvokeMember).
there is an example for Outlook, i tried it for Excel and it works as well.
my example:
<ProjectProperties HostName="Excel" HostPackage="{29A7B9D7-A7F1-4328-8EF0-6B2D1A56B2C1}" OfficeVersion="16.0" VstxVersion="4.0" ApplicationType="Excel" Language="vb" TemplatesPath="" DebugInfoExeName="#Software\Microsoft\Office\16.0\Excel\InstallRoot\Path#excel.exe" DebugInfoCommandLine="/x" AddItemTemplatesGuid="{DCFE8D25-4715-4C33-9EAB-A34A9EBC9544}" />
i changed
OfficeVersion="15.0"
to
OfficeVersion="16.0"
and the path to Excel
#Software\Microsoft\Office\16.0\Excel\
as well, finally it starts in Excel 2016...
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.