Problem
pack asks a chain of separate QuickPicks every time — "Generate and install a development certificate?" then "Bundle Windows App SDK runtime (self-contained)?" — with no memory of previous answers, and if one is dismissed/missed the build silently stalls.
Separately, on an ARM64 machine, pack produced an arm64 self-contained package from an x64 build-output folder with no prompt or warning about the architecture mismatch.
Proposed solution
- Persist answers as workspace settings (
winapp.pack.selfContained, winapp.pack.installCert, winapp.pack.architecture) or as a named pack profile, so repeat packs are a single action.
- Offer a single "Package…" QuickPick summary ("Self-contained ✔ · Install cert ✔ · arm64 — [Change]") instead of a sequential interrogation.
- Surface the target architecture explicitly (defaulted from the RID) and warn on mismatch between the selected build output's arch and the package arch.
Additional context
Observed with microsoft-winappcli.winapp v0.2.1-prerelease.6, VS Code 1.127.0, Windows on ARM. The silent x64→arm64 packaging is a real footgun for anyone shipping architecture-specific builds. Low–medium cost.
Problem
packasks a chain of separate QuickPicks every time — "Generate and install a development certificate?" then "Bundle Windows App SDK runtime (self-contained)?" — with no memory of previous answers, and if one is dismissed/missed the build silently stalls.Separately, on an ARM64 machine, pack produced an arm64 self-contained package from an x64 build-output folder with no prompt or warning about the architecture mismatch.
Proposed solution
winapp.pack.selfContained,winapp.pack.installCert,winapp.pack.architecture) or as a named pack profile, so repeat packs are a single action.Additional context
Observed with
microsoft-winappcli.winappv0.2.1-prerelease.6, VS Code 1.127.0, Windows on ARM. The silent x64→arm64 packaging is a real footgun for anyone shipping architecture-specific builds. Low–medium cost.