Skip to content
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.

Sign up for GitHub

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

[All Hosts] (devx) equivalent-add-ins-unified-manifest #4853

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

[All Hosts] (devx) equivalent-add-ins-unified-manifest #4853

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 25 additions & 2 deletions docs/develop/make-office-add-in-compatible-with-existing-com-add-in.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
title: Make your Office Add-in compatible with an existing COM add-in
description: Enable compatibility between your Office Add-in and equivalent COM add-in.
ms.date: 06/18/2024
ms.date: 10/16/2024
ms.localizationpriority: medium
---

Expand Down Expand Up @@ -30,7 +30,28 @@ Before you can specify an equivalent COM add-in, you must first identify its `Pr
> [!IMPORTANT]
> Applies to Excel, Outlook, PowerPoint, and Word.

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.
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.

# [Unified manifest for Microsoft 365](#tab/jsonmanifest)

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.

```json
"extensions" [
...
"alternates" [
{
"prefer": {
"comAddin": {
"progId": "ContosoCOMAddin"
}
}
}
]
]
```

# [Add-in only manifest](#tab/xmlmanifest)

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.

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

---

> [!TIP]
> 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.

Expand Down