microsoft / microsoft/msix-packaging
MSIX, WPF, and "Start at Login
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.1k
- Forks
- 193
- Avg merge
- 2h 16m
- Merged PRs (30d)
- 2
Description
Recently, I packaged a classic WPF desktop app with MSIX, expecting all the modern Windows benefits—easy deployment, auto-updates, clean uninstalls, and, of course, a way to auto-start the app at login.
🔍 The Truth:
❌ The “Startup Task” feature doesn’t exist for classic WPF+MSIX.
🙅♂️ No “Open at startup” option in the Start menu.
🛑 No manifest hack, no API workaround—unless you refactor to WinUI3/UWP (not practical for most business apps).
🔒 Sandboxing blocks all the old-school registry/startup tricks.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names classic WPF packaged with MSIX but provides no files, tests, or entry points. Start by checking whether the MSIX SDK has an existing startup-task path for classic WPF and clarify the expected supported behavior. Done requires a maintainer-confirmed solution or documented limitation.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100