-
Notifications
You must be signed in to change notification settings - Fork 265
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update the Outlook + Teams sample to Office + Teams sample #1366
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@hermanwenhe add a note here to clarify the office versions
|
||
Now you have the ability to create a single unit of distribution for all your Microsoft 365 extensions by using the same manifest format and schema, based on the current JSON-formatted Teams manifest. | ||
|
||
## This sample illustrates | ||
|
||
- How a Teams Tab and an Outlook add-in share the same JSON manifest in one project. | ||
- How a Teams Tab and an Office add-in share the same JSON manifest in one project. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note
The unified app manifest for Word, Excel, and PowerPoint is in preview. Visit this link to check the required Office Versions.
@@ -86,9 +88,9 @@ Once the provisioning and deployment steps are finished, you can preview your Te | |||
|
|||
- From Teams Toolkit CLI: execute `teamsapp preview --env dev` in your project directory to launch your application. | |||
|
|||
### Preview Outlook add-in | |||
### Preview Office add-in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does the "Deploy to Azure" section also apply to WXP add-ins?
No description provided.