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.
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.
In this doc, it is mentioned that
The following features aren't yet supported in the Developer Preview.
... ...
Publishing add-ins to the Office Store or Office 365 centralized
deployment that use custom functions.
I just want to make sure it means that at the moment we cannot submit to Office Store any add-in that has custom functions; what we can do is only internally deploying add-ins with custom functions, right?
Your interpretation of that guidance in the documentation is correct. i.e., an add-in that uses custom functions cannot currently be published to the Office Store or via Office 365 centralized deployment.
For information about other ways to publish an add-in, see Deploy and publish your Office Add-in.
Was meaning to reply back to this, but add-ins with custom functions are available to be submitted to the Office Store, as announced here: https://developer.microsoft.com/en-us/office/blogs/office-extensibility-build-2019/
Note: Centralized Deployment is still being deployed through all tenants and that will take a few more weeks to complete.
I have written a small officeJS addin for excel which run perfectly on desktop excel client. Also office online from onedrive gives an option of installing the addin from the ribbon menu. I want to use this officeJS addin to run on either of the following configuration:
On premise office online server configured with on premise
sharepoint server.
On premise office online server with my own
implementation of wopi host.
How to deploy an officeJS addin on office online on premise server which is preferably managed centrally by the administrator.
Also why is the add-ins option is not available on the office online configured with sharepoint, pfa image:
office online onedrive v/s office online onprem with sharepoint
Thank You
The Office Online Server currently doesn't enable Office store by default. As part of the configuration, you'd have to enable it. I'm not 100% sure about the exact setting. It may be this: set the AllowExternalMarketplace flag to true.
More here
Try this. On a server in the farm, open the SharePoint Management Shell (PowerShell). Run this command:
Set-OfficeWebAppsFarm - OfficeAddinEnabled:$true
You probably have to be logged in as a farm administrator.
There is some documentation here: Set-OfficeWebAppsFarm
I am new to sharepoint online. At first I need to know the difference between sharepoint online and office 365 preview.
Preview site: https://portal.microsoftonline.com/Admin/Default.aspx which looms like below.
I have also the below site
Now what is the difference between the two. My goal is to create apps and webparts. Which one shall i choose? I have not installed sharepoint 2013 server/ sharepoint foundation. Can i create apps and webparts without installing server2013/foundation2013?
The Office365 Preview is running on the new SharePoint 2013 platform. If you want to build and monetize apps/web parts, you would need to go with this option, as it is the
latest and greatest.
Go to http://dev.office.com to get all of the resources you need including links to the software, tutorials, documentation, etc...
Microsoft provides a free Office365 portal specifically for developers who want to build apps on the online platform. With this, all you would need is Visual Studio 2012 and the SharePoint/Office SDK installed to build apps. You would deploy and debug directly on the online portal without needing SharePoint installed on your environment.
I hope this helps.