Skip to content

Commit dade65a

Browse files
authored
[All Hosts] (devx) equivalent-add-ins-unified-manifest (#4853)
1 parent 3b7e389 commit dade65a

File tree

1 file changed

+25
-2
lines changed

1 file changed

+25
-2
lines changed

docs/develop/make-office-add-in-compatible-with-existing-com-add-in.md

Lines changed: 25 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Make your Office Add-in compatible with an existing COM add-in
33
description: Enable compatibility between your Office Add-in and equivalent COM add-in.
4-
ms.date: 01/30/2025
4+
ms.date: 02/12/2025
55
ms.localizationpriority: medium
66
---
77

@@ -30,7 +30,28 @@ Before you can specify an equivalent COM add-in, you must first identify its `Pr
3030
> [!IMPORTANT]
3131
> Applies to Excel, Outlook, PowerPoint, and Word.
3232
33-
To enable compatibility between your Office Add-in and COM add-in, identify the equivalent COM add-in in the [manifest](add-in-manifests.md) of your Office Add-in. Then, Office on Windows will use the COM add-in instead of the Office Add-in, if they're both installed.
33+
To enable compatibility between your Office Add-in and COM add-in, identify the equivalent COM add-in in the [manifest](add-in-manifests.md) of your Office Add-in. Then, Office on Windows will use the COM add-in instead of the Office Add-in, if they're both installed. The configuration depends on the type of manifest that is being used.
34+
35+
# [Unified manifest for Microsoft 365](#tab/jsonmanifest)
36+
37+
The following example shows the portion of the manifest that specifies a COM add-in as an equivalent add-in. The value of the "alternates.prefer.comAddin.progId" property identifies the COM add-in.
38+
39+
```json
40+
"extensions" [
41+
...
42+
"alternates" [
43+
{
44+
"prefer": {
45+
"comAddin": {
46+
"progId": "ContosoCOMAddin"
47+
}
48+
}
49+
}
50+
]
51+
]
52+
```
53+
54+
# [Add-in only manifest](#tab/xmlmanifest)
3455

3556
The following example shows the portion of the manifest that specifies a COM add-in as an equivalent add-in. The value of the `ProgId` element identifies the COM add-in and the [EquivalentAddins](/javascript/api/manifest/equivalentaddins) element must be positioned immediately before the closing `VersionOverrides` tag.
3657

@@ -46,6 +67,8 @@ The following example shows the portion of the manifest that specifies a COM add
4667
</VersionOverrides>
4768
```
4869

70+
---
71+
4972
> [!TIP]
5073
>
5174
> - For information about COM add-in and XLL UDF compatibility, see [Make your custom functions compatible with XLL user-defined functions](../excel/make-custom-functions-compatible-with-xll-udf.md). Not applicable for Outlook.

0 commit comments

Comments
 (0)