Shared runtime requirement sets
Requirement sets are named groups of API members. Office Add-ins use requirement sets specified in the manifest or use a runtime check to determine whether an Office application supports APIs that an add-in needs. For more information, see Office versions and requirement sets.
Parts of an Office Add-in that run JavaScript code, such as task panes, function files launched from add-in commands, and Excel custom functions, can share a single JavaScript runtime. This enables all the parts to share a set of global variables, to share a set of loaded libraries, and to communicate with each other without having to pass messages through a persisted storage. For more information, see Configure your Office Add-in to use a shared JavaScript runtime.
The following table lists the Shared Runtime requirement sets, the supported Office client applications, and the minimum builds or versions for those applications where applicable.
Requirement set | Office on the web | Office on Windows
|
Office on Windows
|
Office on Mac | Office on iPad |
---|---|---|---|---|---|
SharedRuntime 1.2 | Excel: Supported | Excel: Version 2108 (Build 14326.20508) | Not supported | Excel: 16.52.0.0 | Not supported |
SharedRuntime 1.1 | Excel, PowerPoint, Word: Supported |
|
|
|
Not supported |
Office versions and build numbers
To find out more about versions and build numbers, see:
- Version and build numbers of update channel releases for Microsoft 365 clients
- What version of Office am I using?
Office Common API requirement sets
For information about Common API requirement sets, see Office Common API requirement sets.
SharedRuntime API 1.1
The SharedRuntime API 1.1 is the first version of the API. For details, see the Office.Addin reference topic.
SharedRuntime API 1.2
The SharedRuntime API 1.2 adds the Office.BeforeDocumentCloseNotification interface, which helps ensure that workbooks don't close while an add-in process is running.
Important
SharedRuntime 1.2 is only supported in Excel.
See also
Office Add-ins
피드백
https://aka.ms/ContentUserFeedback
출시 예정: 2024년 내내 콘텐츠에 대한 피드백 메커니즘으로 GitHub 문제를 단계적으로 폐지하고 이를 새로운 피드백 시스템으로 바꿀 예정입니다. 자세한 내용은 다음을 참조하세요.다음에 대한 사용자 의견 제출 및 보기