Skip to content

Commit fd357f3

Browse files
[All hosts] (manifest) Update image (#5089)
1 parent 74a8e1d commit fd357f3

File tree

2 files changed

+9
-9
lines changed

2 files changed

+9
-9
lines changed

docs/develop/convert-xml-to-json-manifest.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.localizationpriority: medium
1111
To add Teams capabilities to an add-in that uses the add-in only manifest, or to just future proof the add-in, you need to convert it to use the unified manifest for Microsoft 365.
1212

1313
> [!NOTE]
14-
>
14+
>
1515
> - Projects created in Visual Studio, as distinct from Visual Studio Code, can't be converted at this time.
1616
> - If you [created the project with Teams Toolkit](teams-toolkit-overview.md) or with the "unified manifest" option in the [Yeoman generator for Office Add-ins (Yo Office)](yeoman-generator-overview.md), it already uses the unified manifest.
1717
@@ -26,7 +26,7 @@ There are three basic tasks to converting an add-in project from the add-in only
2626
[!INCLUDE [non-unified manifest clients note](../includes/non-unified-manifest-clients.md)]
2727

2828
> [!NOTE]
29-
>
29+
>
3030
> - Add-ins that use the unified manifest can be sideloaded only on Office Version 2304 (Build 16320.20000) or later.
3131
> - Projects created in Visual Studio, as distinct from Visual Studio Code, can't be converted at this time.
3232
> - If you [created the project with Teams Toolkit](teams-toolkit-overview.md) or with the "unified manifest" option in the [Office Yeoman Generator](yeoman-generator-overview.md), it already uses the unified manifest.
@@ -41,12 +41,12 @@ To avoid conflicts with UI control names and other problems, be sure the existin
4141

4242
### Ensure that you have two special image files
4343

44-
If your add-in only manifest doesn't already have both **\<IconUrl\>** and **\<HighResolutionIconUrl\>** (in that order) elements, then add them just below the **\<Description\>** element. The values of the **DefaultValue** attribute should be the full URLs of image files. The images must be a specified size as shown in the following table.
44+
If your add-in only manifest doesn't already have both **\<IconUrl\>** and **\<HighResolutionIconUrl\>** (in that order) elements, then add them just below the **\<Description\>** element. The values of the **DefaultValue** attribute should be the full URLs of image files. The images must be a specified size as shown in the following table.
4545

4646
|Office application|\<IconUrl\>|\<HighResolutionIconUrl\>|
4747
|:---------------|:---------------|:---------------|
4848
|Outlook|64x64 pixels|128x128 pixels|
49-
|All other Office</br>applications|32x32 pixels|64x64 pixels|
49+
|All other Office</br>applications|32x32 pixels|64x64 pixels|
5050

5151
The following markup is an example.
5252

@@ -72,7 +72,7 @@ The following markup is an example.
7272

7373
1. Be sure that the domain segment of the add-in's URLs in the manifest are pointing to `https://localhost:3000`.
7474

75-
1. If your manifest has any **\<FunctionName\>** elements, make sure their values have fewer than 65 characters.
75+
1. If your manifest has any **\<FunctionName\>** elements, make sure their values have fewer than 65 characters.
7676

7777
> [!IMPORTANT]
7878
> The value of this element must exactly match the name of an action that's mapped to a function in a JavaScript or TypeScript file with the [Office.actions.associate](/javascript/api/office/office.actions#office-office-actions-associate-member(1)) function. If you change it in the manifest, be sure to change it in the `actionId` parameter passed to `associate()` too.
@@ -81,13 +81,13 @@ The following markup is an example.
8181

8282
1. Validate the modified add-in only manifest. See [Validate an Office Add-in's manifest](../testing/troubleshoot-manifest.md).
8383

84-
1. Verify that the add-in can be sideloaded and run. See [Sideload an Office Add-in for testing](../testing/test-debug-office-add-ins.md#sideload-an-office-add-in-for-testing).
84+
1. Verify that the add-in can be sideloaded and run. See [Sideload an Office Add-in for testing](../testing/test-debug-office-add-ins.md#sideload-an-office-add-in-for-testing).
8585

8686
Resolve any problems before you attempt to convert the project.
8787

8888
## Conversion tools and options
8989

90-
There are several ways to carry out the remaining tasks, depending on the IDE and other tools you want to use for your project, and on the tool you used to create the project.
90+
There are several ways to carry out the remaining tasks, depending on the IDE and other tools you want to use for your project, and on the tool you used to create the project.
9191

9292
- [Convert the project with Teams Toolkit](#convert-the-project-with-teams-toolkit)
9393
- [Convert projects created with the Yeoman generator for Office Add-ins (aka "Yo Office")](#convert-projects-created-with-the-yeoman-generator-for-office-add-ins-aka-yo-office)
@@ -115,7 +115,7 @@ The easiest way to convert is to use Teams Toolkit.
115115

116116
1. The **App Features Using an Office Add-in** dropdown menu opens. The options listed will vary depending on your version of Teams Toolkit. Select **Import an Existing Office Add-in**.
117117

118-
:::image type="content" source="../images/teams-toolkit-create-office-task-pane-capability.png" alt-text="The options in the App Features Using an Office Add-in dropdown menu. One option is called 'Import an Existing Office Add-in'.":::
118+
:::image type="content" source="../images/teams-toolkit-create-office-import-capability.png" alt-text="The options in the App Features Using an Office Add-in dropdown menu. The 'Import an Existing Office Add-in' option is selected.":::
119119

120120
1. In the **Existing add-in project folder** dropdown menu, browse to the root folder of the add-in project.
121121
1. In the **Select import project manifest file** dropdown menu, browse to the add-in only manifest file, typically named **manifest.xml**.
@@ -129,7 +129,7 @@ You can sideload the add-in using the Teams Toolkit or in a command prompt, bash
129129
- [Sideload with Teams toolkit](../testing/sideload-add-in-with-unified-manifest.md#sideload-with-the-teams-toolkit)
130130
- [Sideload with a system prompt, bash shell, or terminal](../testing/sideload-add-in-with-unified-manifest.md#sideload-with-a-system-prompt-bash-shell-or-terminal)
131131

132-
> [!NOTE]
132+
> [!NOTE]
133133
> Add-ins that use the unified manifest can be sideloaded only on Office Version 2304 (Build 16320.20000) or later.
134134
135135
### Convert projects created with the Yeoman generator for Office Add-ins (aka "Yo Office")
115 KB
Loading

0 commit comments

Comments
 (0)