You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/develop/convert-xml-to-json-manifest.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ ms.localizationpriority: medium
11
11
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.
12
12
13
13
> [!NOTE]
14
-
>
14
+
>
15
15
> - Projects created in Visual Studio, as distinct from Visual Studio Code, can't be converted at this time.
16
16
> - 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.
17
17
@@ -26,7 +26,7 @@ There are three basic tasks to converting an add-in project from the add-in only
> - Add-ins that use the unified manifest can be sideloaded only on Office Version 2304 (Build 16320.20000) or later.
31
31
> - Projects created in Visual Studio, as distinct from Visual Studio Code, can't be converted at this time.
32
32
> - 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
41
41
42
42
### Ensure that you have two special image files
43
43
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.
|All other Office</br>applications|32x32 pixels|64x64 pixels|
49
+
|All other Office</br>applications|32x32 pixels|64x64 pixels|
50
50
51
51
The following markup is an example.
52
52
@@ -72,7 +72,7 @@ The following markup is an example.
72
72
73
73
1. Be sure that the domain segment of the add-in's URLs in the manifest are pointing to `https://localhost:3000`.
74
74
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.
76
76
77
77
> [!IMPORTANT]
78
78
> 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.
81
81
82
82
1. Validate the modified add-in only manifest. See [Validate an Office Add-in's manifest](../testing/troubleshoot-manifest.md).
83
83
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).
85
85
86
86
Resolve any problems before you attempt to convert the project.
87
87
88
88
## Conversion tools and options
89
89
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.
91
91
92
92
-[Convert the project with Teams Toolkit](#convert-the-project-with-teams-toolkit)
93
93
-[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.
115
115
116
116
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**.
117
117
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.":::
119
119
120
120
1. In the **Existing add-in project folder** dropdown menu, browse to the root folder of the add-in project.
121
121
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
129
129
-[Sideload with Teams toolkit](../testing/sideload-add-in-with-unified-manifest.md#sideload-with-the-teams-toolkit)
130
130
-[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)
131
131
132
-
> [!NOTE]
132
+
> [!NOTE]
133
133
> Add-ins that use the unified manifest can be sideloaded only on Office Version 2304 (Build 16320.20000) or later.
134
134
135
135
### Convert projects created with the Yeoman generator for Office Add-ins (aka "Yo Office")
0 commit comments