I have made a OneNote add-in, as specified here. All local tests were successful.
This project is a prototype for the development of a proprietary OneNote add-in for a client. Hence the add-in will not be published to the Office Store.
I will not be giving a development phase add-in for my clients so following Microsoft's publishing guide here, I have hosted the add-in as a Static Website on Azure. This process has provided me with a permanent link where the add-in will reside.
Using the guide provided by Microsoft, add-ins will be able to be loaded from a local manifest.xml file. but there is no input for loading the add-in from a url.
My question is, how can the client load the add-in from the link provided?
Related
I've installed Microsoft office web apps offline in the VM and also Installed SharePoint 2016 in another VM machine. Both VMs are connected to the domain.
Besides, I've successfully connected SharePoint to the office farm. But when I try to open docx files or any other office app on the web browser I get the below error :
Failed to launch 'ms-word:ofv%7Cu%7Chttp://....' because the scheme
does not have a registered handler.
Based on the error that you have screenshoted, the Application falied to launch the MS Word Desktop Client because the scheme "ms-word" does not have a handler registered, which in simple terms means that there isn't any associated app to execute when the beforementioned scheme is used and in order to have the scheme registered with an application, you would have to install Microsoft Office on the machine that you are using to view the SharePoint Site.
Here is the link to the documentation where is states that the scheme handlers are registered upon the installation of Microsoft Office.
The following is the list of scheme names implemented in Microsoft Office applications. When Microsoft Office is installed, each scheme name is registered with Windows to be handled by the Office product of the same name. Note that "ms-spd" is an abbreviation for SharePoint Designer.
ms-word:
But in order to use the Web counterparts of the Office apps, like Word or Excel in the browser, there is a different procedure where it is required of you to Install a Office Online Server and enable communication with SharePoint Server.
As it is written in the overview of the product...
Office Online Server delivers browser-based versions of Word, PowerPoint, Excel, and OneNote. A single Office Online Server farm can support users who access Office files through SharePoint Server, Exchange Server, shared folders, and web sites.
Since it's a lengthy procedure and there are different prerequisites in term of licensing and other matters, you can check out this link (Configure Office Online Server for SharePoint Server) on the topic and decide which features you are looking for.
I have an OfficeJS Excel add-in that I want to deploy in an environment, where neither centralized deployments, nor a SharePoint catalog is available for distribution.
Loading the add-in via a shared network drive works, but according to the microsoft docs this is not an option for a production deployment.
Other add-ins in that environment are all VSTO based.
Now my question is, if it's somehow possible to deliver the web-based add-in via a VSTO wrapper?
Would it alternatively be possible to provide the manifest on the the local drive for each user somehow?
EDIT:
Just to make it clearer - still want to serve the web-app via a server. I basically only want to distribute the manifest differently.
Loading the add-in via a shared network drive works, but according to the microsoft docs this is not an option for a production deployment.
When production options are not available, all other possible ways are good.
my question is, if it's somehow possible to deliver the web-based add-in via a VSTO wrapper?
To deliver the manifest is not enough, so you need to sideload the add-in by adding the manifest file to the Office application. Isn't better to provide URL to the network share where manifest resides to users? VSTO is useless in that scenario. OfficeJS (not Excel) doesn't provide any API for loading web add-ins programmatically.
Would it alternatively be possible to provide the manifest on the the local drive for each user somehow?
There is no need to keep the manifest on the local drive. You can provide URL of the manifest to sideload the add-in if the centralized deployment is not available (via the Office365 admin center).
Read more about possible routes in the Deploy and publish Office Add-ins article.
My custom Office Excel add-in does not work in my DEV environment (1) with the following three VMs.
Proper DEV on-prem environment:
AD Domain Controller
SharePoint 2016 on-prem
Office Online Server (updated November 2018)
OOS works as I can open Office docs in the browser. Both SharePoint and OOS run on http.
Online environment (just to test add-in itself):
I have tested the same - sample Excel add-in generated by Yeoman - in different environment too: O365 and SharePoint Online (developer tenant). It works, manifest is added to Apps for Office in AppCatalog and server works on https://localhost. I can see task pane of add-in in the browser. I can also debug both: desktop and web.
The same add-in (with server running on https://localhost) which works in online environment (2), does not work in DEV environment (1). It does not work when I upload XML manifest to AppCatalog, and it does not work when I try to debug generated add-in too.
I saw Excel add-in working in Internet Explorer on environment also with SharePoint 2016 and Office Online Server (/Office Web Apps). However, I do not have more details about that environment and how this add-in has been installed.
I have deployed an Office Add-in and uploaded through the O365 Admin Center The Add-In appears in the Excel Ribbon but can use it as a message appears “We could not open the Add-In from LocalHost.
Should I modify anything in the Manifest File?
The Add-In was created with Yeoman and it´s addressed to “LocalHost:3000”.
It´s just a template (taskpane example)
Many thanks in advance!!!
Regards,
José.
Localhost is only used to host the add-in during development. If you have deployed the add-in with Centralized Deployment, then you should be hosting the add-in on a web server or cloud account. In that case, the URLs in the manifest should be changed to the domain that is hosting the add-in.
I started recently to build a office add-in (the web-based ones, not VSTO) and I would like in addition to have it in the office store (the preferred method of distribution) to also distribute the manifest through a setup file. Is this possible?
I searched around the web but the only things that come up are for VSTO add ons.
Web add-ins are not designed for distributing via standalone installers like MSI. You/administrator can sideload them for the organization unit (OU) or just install them from the store. See Centralized Deployment via the Office 365 admin center for more information.