Draft
Conversation
Add two sample apps demonstrating multiple Application elements in a single package manifest, supporting the multi-headed MSIX packaging feature (WindowsAppSDK #5586): - cs-winui-msix: WinUI 3 primary app + console secondary app in one MSIX package via single-project packaging - cs-wpf-sparse: WPF primary app with register/unregister UI + WPF secondary app in one sparse package Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Samples/MultiHeadedPackage/demonstrating multiple<Application>elements in a single package manifestThese samples support the multi-headed MSIX packaging feature added in WindowsAppSDK (microsoft/WindowsAppSDK#5586).
Description
Multi-headed packages contain multiple
<Application>entries in a singlePackage.appxmanifest. Each application gets its own Start menu tile and can be launched independently, while sharing the same package identity and installation lifecycle.The MSIX sample uses single-project MSIX packaging. The primary WinUI app owns the manifest and uses
$targetnametoken$tokens. The secondary console app is included via<ProjectReference>with its executable hardcoded in the manifest asSecondaryApp.exewithEntryPoint="Windows.FullTrustApplication". After deployment, both apps appear as separate Start menu entries.The sparse sample demonstrates the same multi-headed pattern with runtime-registered sparse packages. The primary WPF app provides Register/Unregister/Restart buttons using
PackageManager.AddPackageByUriAsync. The secondary WPF app usesGetCurrentPackageFullNameto detect whether it has package identity, which it will once the sparse package is registered.🤖 Generated with Claude Code