交付包裹在VSTO ADDIN中的Officejs Web addin
我有一个我想在环境中部署的Officejs Excel加载项,在该环境中,集中部署和SharePoint目录都无法分发。
通过共享网络驱动器加载加载项,但是根据Microsoft文档,这不是生产部署的选项。
在该环境中的其他加载项都是基于VSTO的。
现在我的问题是,是否可以通过VSTO包装器以某种方式传递基于Web的加载项?
或者,可以以某种方式为每个用户提供本地驱动器上的清单吗?
编辑: 只是为了使其更清楚 - 仍然希望通过服务器使用Web -App。我基本上只想以不同的方式分发清单。
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.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
如果没有生产选项,所有其他可能的方法都很好。
要交付清单还不够,因此您需要通过将清单文件添加到Office应用程序中来进行加载项。将URL提供给网络共享的URL是否更好地占有用户?在这种情况下,VSTO是毫无用处的。
Officejs
(不是Excel)不提供任何以编程加载Web加载的API。无需将清单保留在本地驱动器上。如果没有集中式部署(通过Office365 Admin Center),则可以提供清单的URL来侧载加载项。
在部署和发布添加办公室添加办公室添加办公室添加-ins 文章。
When production options are not available, all other possible ways are good.
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.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.