I Have an add-in that is working on Excel in chrome, excel in Edge, but doesn't work in excel desktop.
Any clues?
Thanks
In the article amitklein gave, it says:
Office will still use the EdgeHTML base for add-ins until a build of Office 365 that supports Chromium is installed on the computer. We expect these builds to ship in 2020. They will likely appear in the Insiders channel in the first half of the year.
I haven't found the Chromium based Office 365 in insider channel so I think the version for now is still EdgeHTML based and Excel uses Edge Legacy.
Related
Is it possible to develop an Excel-VBA application for i.e. version 2012, but using version 365?
Reason for this question is that I sometimes develop clean VBA applications for clients in 365, but when executing in their environment the code breaks for countless errors, mostly not finding certain command names. Currently, I find myself developing the VBA applications for older versions on the clients' computers as a workaround.
One of my add-ins, Formula Formatter, works well in Office 365. However, one client told me it cannot be loaded in Office Professional Plus 2016.
Does anyone know what may be the reason? Should we do something special in the manifest xml for Office Professional Plus 2016?
In its manifest, Formula Formatter specifies the requirement set ExcelAPI with a minimum version of 1.2. Per the documentation for that requirement set (https://dev.office.com/reference/add-ins/requirement-sets/excel-api-requirement-sets) your customer will need to be running "Version 1601 (Build 6741.2088) or later". Customers that have a non-subscription version of Office won't have that requirement set.
If you remove the requirement set from the manifest, your add-in would be available on Office 2016 but you would need to ensure that your add-in has a good user experience when they are not present.
I would like to develop Add-in for office Word for Mac (2011 and later). But I cannot find any manuals about Add-Ins development.
Can anybody know how to develop Add-Ins for Office for Mac?
It will be good if anybody suggest me link of Example. I have tried but didn't get any sample.
The good news is that you can use almost all the APIs documented here for MAC as well!
You also want to read this article about how to try your add-ins in MAC or iOS.
Finally make sure you are on the latest possible build! (15,22 as of right now).
Happy coding!!!
The process for building JavaScript add-ins for Mac is pretty much the same as building them for other platforms. There are some specific instructions for debugging on Mac.
However, Office Add-Ins for Mac are only supported starting with Office for Mac 2016 (and even then I believe it needs to be a recent update).
With the introduction of Excel on Android and iOS, I'm not sure what's the correct method of creating a UDF (User Defined Function) that will work across all versions of the Office 365?
I want my UDF to work on iPad, Android as well as Desktop. What's the official Microsoft way of supporting all of these versions of Office for UDF's?
There is no way to support all these platforms. It will work on the Desktop editon of Office.
I have a couple of Excel Add ins. If I move to Office 365, will these add ins be available ? Is there any development support(VSTO) for Office 365 ?
I to have been curious about the answer to this, so went looking online. From the following site, I'd say the answer is no. It looks like developing for Office 365 is more along the lines of SharePoint development.
http://blogs.msdn.com/b/donovanf/archive/2011/06/29/office-365-developer-guidance-and-resources.aspx
I have seen advertisements online for products such as this... http://www.ocxt.com/products that look like they could provide a possible solution for taking a vsto application to the web.
I think things have moved on substantially since this question was asked. Microsoft seem to be fully committed to the Add-in approach with Office 2013 and the equivalent VSTO tooling available in VS2012.
The Office Dev Center home page has Office 2013 and VSTO Add-ins written all over it.
This MSDN Blog Post also clearly shows Add-ins are still part of the strategy.
Until the full capabilities of Desktop MS Office are available in a browser, I can't see this situation changing.
If you mean Office 365 installed on client PC then there is no issue with VSTO Add-ins. Our Chem4Word Add-in is using Office 2010 VSTO and happily works with 2010, 2013, 2016, 2019, O365.
If you mean Office 365 on-line then you have to redesign them using the Office 365 Javascript API