![]() It applies only to the root pane of the add-in.There are two exceptions to this behavior. If it tries to go to a URL that isn't in the list, then, in desktop Office, that URL opens in a new browser window (outside the add-in pane). If the add-in tries to go to a URL in a domain that is in the list, then it opens in the task pane in both Office on the web and desktop. To override this (desktop Office) behavior, specify each domain you want to open in the add-in window in the list of domains specified in the AppDomains element of the manifest file. However, in desktop platforms, if your add-in tries to go to a URL in a domain other than the domain that hosts the start page (as specified in the SourceLocation element of the manifest file), that URL opens in a new browser window outside the add-in pane of the Office application. When running in Office on the web, your task pane can be navigated to any URL. Specify domains you want to open in the add-in window ![]() ![]() Only use the AppDomains element to specify domains other than the one specified in the SourceLocation element for authentication scenarios. For more information, see Validation policies for apps and add-ins submitted to AppSource. Various GUID generator tools are available on the web that you can use to create a unique GUID.Īdd-ins submitted to AppSource must also include the SupportUrl element. Make sure that the add-in ID is a valid and unique GUID. Best practices for submitting to AppSource Self-signed certificates can be used for development and testing, so long as the certificate is trusted on the local machine. If your add-in accesses external data and services, it should be SSL-secured to protect data in transit. If you plan to run your add-in in Office on the web or publish your add-in to AppSource, it must be SSL-secured. Add-ins that are not SSL-secured (HTTPS) generate unsecure content warnings and errors during use. While not strictly required in all add-in scenarios, using an HTTPS endpoint for your add-in is strongly recommended. The server hosting the image should not return a Cache-Control header specifying no-cache, no-store, or similar options in the HTTP response.Īll URLs, such as the source file locations specified in the SourceLocation element, should be SSL-secured (HTTPS). Hosting requirementsĪll image URIs, such as those used for add-in commands, must support caching. ** SupportUrl is only required for add-ins that are distributed through AppSource. *Added in the Office Add-in Manifest Schema version 1.1. Set* Sets (Requirements)* Sets (MailAppRequirements)* Permissions (ContentApp) Permissions (TaskPaneApp) Permissions (MailApp) SourceLocation (ContentApp) SourceLocation (TaskPaneApp) SourceLocation (MailApp) Required elements by Office Add-in type ElementĭefaultSettings (ContentApp) DefaultSettings (TaskPaneApp) For more information see How to find the proper order of manifest elements. There is also a mandatory order in which elements must appear within their parent element.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |