Office 2016 has been released, where can I get the list of the control IDs?
Searching the microsoft.com site I can only find office 2007-2013 control identifiers.
Microsoft has published the help files for Office 2016. You can get it from:
https://www.microsoft.com/en-us/download/details.aspx?id=50745
They were not published yet. Try to use for Office 2013 or wait until Microsoft publishes the full list of controls for Office 2016.
UPDATE: The list of Office 2016 ribbon control IDs is available for download.
Related
On an Intranet web page, I have a link to an Excel document that resides on a network drive, like so:
ms-excel:ofv|u|file:///N:/folder/file.xlsx
This is an office protocol handler described here.
On computers with Office 2019 installed, the Excel document opens with the registered application (Excel) without problems; on computers with Office 2016 I get the following error:
The action couldn't be performed because Office doesn't recognize the command it was given.
I compared the registry keys at \HKEY_CLASSES_ROOT\ms-excel\ and they are basically the same (of course the path to protocolhandler.exe is different).
When I execute protocolhandler.exe on the command line on the computers with Office 2016, I always get the above error regardless of how I try to launch an Excel or Word document (e.g. ms-excel:ofv|u|file:///... or ms-word:ofv|u|http://...)
Versions of Office:
Office Professional Plus 2019 Version 1808 (Build 10382.20010 click-and-run) 64-bit
Office Professional Plus 2016 Version 16.0.5266.1000 MSO 64-bit
Is there any way to make the protocol handler work with Office 2016?
As you can imagine, that exe handles all the different protocols integrated into MS products. Because of this, every variation of office (or windows) need to have their very own version of this file, in order to operate correctly. Which is also why this file comes deeply embedded within the Office product folder.
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 just Use AJAX Library from WebDAV library to start WebDAV in browsers other than IE with your information from
http://www.webdavsystem.com/ajax/programming/opening_ms_office_docs/
And This is result:
Microsoft Office 2013
IE:Protocol ext ==> ok
Chrome:Protocol ext ==>ok
FF:Protocol ext ==> ok
Microsoft Office 2010
IE:ActiveX ==> ok
Chrome:Plugin2 ==>fault
FF:Add-on ==>ok
Microsoft Office 2007 and earlier
IE:ActiveX ==>ok
Chrome:Java applet2 ==> fault
FF:Java applet ==>ok
I can not run editing document when run in chrome (version 45) from Microsoft Office 2010, Microsoft Office 2007 and earlier.
please support us to run on Chrome.
I have attached my demo, please help me solve this problem:
http://www.mediafire.com/download/6kv2d8zcq47w9fj/TestWebDavHtml.rar
Thank you very much!
First of all make sure you are using the IT Hit WebDAV Ajax Library v5 or later.
Regarding MS Office 2010:
Make sure you have Microsoft Office 2010 SP2 or later installed. Also verify that you have all Windows updates installed. WebDAV components are updated rapidly and may fix some issues.
Regrding MS Office 2007:
In general MS Office 2007 and earlier are not supported any more by Microsoft. However you still can open documents using it:
Make sure you have all MS Office and Windows updates installed.
Make sure you have a latest WebDAV Ajax Library v5 or later, client protocol application installed and web browser extension enabled.
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
I have a site developed in Microsoft Office SharePoint server 2007 and I have installed Microsoft office 2010 on my machine. When I try to access excel file stored in document library. It gives me an error saying that it requires a Windows SharePoint Services compatible application.
It was working fine when I have Microsoft office 2007. So I am confused whether SharePoint is compatible with office 2010 or not...?
Thanks
Sachin
Yes it is compatible and it should work. A number of things could be going on.
The OWSSUPP.DLL may not be registered correctly.
You could register it manually or reinstall
If you have the 64 bit version of office there are some known issues opening data in SharePoint.
http://www.knowsharepoint.com/2010/06/sharepoint-datasheet-view-and-office.html
Windows SharePoint Services Support files may not be installed.
in this case install these through Add/Remove programs. It's in the office tools section of the MS Office application.
If you have some applications that were part of Office 2003 or earlier you may need to uninstall them.