microsoft / microsoft/WindowsAppSDK

Single-project packaging should support multiple executables

Open
#5,586 6 comments 6 reactions 1 assignee View on GitHub

@guimafelipe is already working on this.

Since Feb 5, 2026.

area-MSIXBuildTools needs-triage
Dominant language
C++
Stars
4.7k
Forks
471
Avg merge
3d 13h
Merged PRs (30d)
28

Description

### Describe the bug

The only remaining gap between single-project and wapproj-based solutions is support for multiple executables (multi-headed packages):
https://github.com/MicrosoftDocs/windows-dev-docs/blob/docs/hub/apps/windows-app-sdk/single-project-msix.md#limitations

If this capability can be delivered, then the wapproj project templates can be completely obsoleted and removed from the component VSIXes in the VS Installer.

### Steps to reproduce the bug

N/A

### Expected behavior

_No response_

### Screenshots

_No response_

### NuGet package version

None

### Packaging type

_No response_

### Windows version

_No response_

### IDE

_No response_

### Additional context

_No response_

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.