Office-js:在 Office 商店中更新加载项的最佳实践 [英] Office-js: Best practices for updating Add-ins in the Office Store
问题描述
我们的开发人员创建了一个 Office 商店应用(在本方案中为 Outlook 应用).每次他们对加载项进行哪怕是很小的更改时,我们都需要重新提交给商店进行认证、批准.
Our developers created an Office store app (in this scenario, Outlook app). Every time they made even a small change to the add-in, then we need to resubmit to the store for certification, approval.
- 这有必要吗?
- 即使我们只是做一些小的更改(比如打字错误),我们是否可以对应用进行更改(因为我们将它托管在我们的服务器上),或者我们是否需要重新提交任何更改?
- 何时重新提交加载项,我们应该遵循哪些规则或协议?
任何指针都会有帮助
推荐答案
Office 加载项仅由两部分组成:
An Office Add-in is comprised of just two things:
- 一个普通"网站,它的特殊之处在于它包含了
Office.js
库 - 一个清单文件,供商店(或 SharePoint 或 Exchange 目录)使用.
就网站 (#1) 而言,您可以根据需要随时更新.它只是一个网站.每天发布,甚至自动从 git repo 推送到它.这是您的网站.
As far as the website (#1) goes, you can updated it as often as you want. It is just a website. Publish to it daily, or even automatically push to it from a git repo. It's your site.
就清单 (#2) 而言,您必须通过 Store 进行处理.但这里的变化通常很少而且相距甚远.例如,您应该只接触清单以更改相当基本的内容,例如名称、网址等.在加载项命令(功能区 UI)的情况下,如果您添加新按钮或更改文本/图标,您也将接触清单……但即便如此,此处的流失应该far 小于网站部分.
As far as the manifest (#2) goes, that you do have to process through the Store. But changes here are generally few and far-between. E.g., you should only be touching the manifest to change fairly basic things, like name, url, and so forth. In the case of Add-in commands (Ribbon UI), you'll also be touching the manifest if you're adding new buttons or changing texts/icons... but even so, the churn here should be far less than on the site portion.
这篇关于Office-js:在 Office 商店中更新加载项的最佳实践的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!