Document COM server support in MSIX packages - #505
Conversation
Add focused guidance for COM server, interface, and type library manifest registration in MSIX packages. Reference ADO bug 26070760. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 4b5b11f6-6bf8-4401-90b8-68f710728c8e
|
Learn Build status updates of commit 28a4ed5: ✅ Validation status: passed
For more details, please refer to the build report. |
There was a problem hiding this comment.
Pull request overview
Adds a new documentation page describing how to declare COM servers, interfaces, proxy stubs, and type libraries in MSIX package manifests (focused on the com4 schema), and links it into the desktop packaging docs navigation.
Changes:
- Add new conceptual article: COM support in MSIX packages with schema guidance, scenario table, and a manifest example.
- Add navigation entry in
toc.ymlunder “Key concepts to know before packaging”. - Add the new article to the “Extend your packaged applications” overview table.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| msix-src/toc.yml | Adds the new COM support article to the desktop packaging TOC. |
| msix-src/desktop/extend-overview.md | Adds a link to the new COM support article in the extension overview table. |
| msix-src/desktop/com-support.md | New documentation page describing packaged COM registration via com4 manifest extensions, including an example and reference links. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| The `com4` schema is a superset and replacement for the older `com`, `com2`, and `com3` | ||
| syntax. Use `com4` for new Windows 11 package manifests that can depend on Windows 10 | ||
| Build 20348 or later. If your package must install on earlier Windows versions, review the | ||
| older namespace schema and validate the manifest against every target OS version. |
There was a problem hiding this comment.
Clarified. The paragraph now cites the [com4:Extension schema reference] for the minimum OS version, notes that build 20348 is the Windows Server 2022 build, states Windows 11 meets the requirement, and frames the guidance as "use com4 when your app targets Windows 11 or later."
| <!-- SME question: Should this article include a tested example for multiple com4:Version | ||
| children under one com4:TypeLib, including the expected behavior when a class references one | ||
| VersionNumber? --> |
There was a problem hiding this comment.
The trailing HTML "SME question" comment is no longer in the file (removed in the current revision), so it won't ship in the published markdown.
Clarify com4 version support, complete the schema links, and remove internal notes. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
Learn Build status updates of commit c62ed0d: ✅ Validation status: passed
For more details, please refer to the build report. |
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 485b92b6-ded3-49ac-8734-e0badb78eb39
|
Learn Build status updates of commit b651193: ✅ Validation status: passed
For more details, please refer to the build report. |
Add focused guidance for COM server, interface, and type library manifest registration in MSIX packages. Reference ADO bug 26070760.