Skip to content

[Excel PowerPoint Word] (devx) clarify add-in only manifest markup for COM/VSTO/Web add-in compatibility #5439

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

Merged
merged 2 commits into from
Oct 28, 2025
Merged

[Excel PowerPoint Word] (devx) clarify add-in only manifest markup for COM/VSTO/Web add-in compatibility #5439

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d654ec9
[Excel PowerPoint Word] (devx) clarify add-in only manifest markup fo…
Rick-Kirkham Oct 28, 2025
9ebbcb1
date
Rick-Kirkham Oct 28, 2025
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
4 changes: 3 additions & 1 deletion 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: 10/24/2025
ms.date: 10/28/2025
ms.localizationpriority: medium
---

Expand Down Expand Up @@ -252,6 +252,8 @@ The following is an example. The **\<Effect\>** element must be after all the **
</VersionOverrides>
```

> [!NOTE]
> The **\<Type\>** value is "COM" for historical reasons, but it refers to either a COM or a VSTO add-in. Similarly, the **\<ProgId\>** value can be either the progId of a COM add-in or the name of a VSTO add-in.
---

## See also
Expand Down