Project 11: Create a Modern MSIX Package
You will package one of your existing C++ applications (like the
my_lstool) as a modern MSIX package. This will involve creating a manifest, assigning an identity, and generating a signed package that can be installed with a double-click.
Quick Reference
| Attribute | Value |
|---|---|
| Primary Language | XML (for manifest) |
| Alternative Languages | N/A |
| Difficulty | Level 2: Intermediate |
| Time Estimate | Weekend |
| Knowledge Area | Deployment / Installers |
| Tooling | MSIX, Windows Application Packaging Project |
| Prerequisites | A working C++ application. Visual Studio 2019 or newer. |
What You Will Build
You will package one of your existing C++ applications (like the my_ls tool) as a modern MSIX package. This will involve creating a manifest, assigning an identity, and generating a signed package that can be installed with a double-click.
Why It Matters
This project builds core skills that appear repeatedly in real-world systems and tooling.
Core Challenges
- Creating a Packaging Project in Visual Studio → maps to using the “Windows Application Packaging Project” template
- Configuring the
Package.appxmanifest→ maps to defining the application’s identity, capabilities, and entry point - Handling application assets → maps to providing icons and logos in various required sizes
- Signing the package → maps to creating a temporary self-signed certificate for testing
Key Concepts
- MSIX Introduction: Microsoft Docs - What is MSIX?
- App Manifest: Microsoft Docs - App package manifest
- Package Signing: Microsoft Docs - Sign an app package
Real-World Outcome
Deliver a working demo with observable output that proves the feature is correct.
Implementation Guide
- Reproduce the simplest happy-path scenario.
- Build the smallest working version of the core feature.
- Add input validation and error handling.
- Add instrumentation/logging to confirm behavior.
- Refactor into clean modules with tests.
Milestones
- Milestone 1: Minimal working program that runs end-to-end.
- Milestone 2: Correct outputs for typical inputs.
- Milestone 3: Robust handling of edge cases.
- Milestone 4: Clean structure and documented usage.
Validation Checklist
- Output matches the real-world outcome example
- Handles invalid inputs safely
- Provides clear errors and exit codes
- Repeatable results across runs
References
- Main guide:
LEARN_WINDOWS_SYSTEMS_PROGRAMMING_CPP.md - N/A, rely on Microsoft’s official documentation.