WinApp CLI 0.3.2 Adds MSIX Bundling and Smarter Init

Native Bundling and Smarter Project Discovery

If you have ever spent an afternoon wrangling separate build pipelines for x64 and ARM64 Windows apps, you know the packaging process can be tedious. Microsoft wants to fix that. The newly released Windows App Development CLI v0.3.2 targets the exact friction points that desktop developers face when shipping software. We have been watching the evolution of this command-line tool closely, and this release introduces native multi-architecture bundling and smarter directory discovery right to your terminal.

Summary

Software Engineer Zachary Teutsch announced the release of Windows App Development CLI v0.3.2, bringing highly requested automated workflows to the public preview tool. The standout addition is native MSIX bundle support through the winapp pack command. Instead of managing multiple architecture outputs manually, developers can now combine x64 and ARM64 builds into a single .msixbundle file using a single terminal command. This satisfies the Microsoft Store's strict format requirements for multi-architecture submissions out of the box.

Project initialization also receives a major intelligence upgrade. The winapp init command now auto-detects compatible projects inside a directory. If you run it within a complex project structure or monorepo, it displays an interactive selection menu mapping out C++, .NET, Electron, Flutter, Rust, and Tauri projects. It automatically places configuration files relative to the chosen project and warns you if you are operating in an incompatible root directory.

For automated environments, the tool includes a -use-defaults flag to bypass prompts during CI/CD scripting. Additional quality-of-life updates include higher quality UI screenshots via winapp ui screenshot that preserve native rounded window corners without ugly black borders, and daily automatic update checks.

Developer Impact

What this means for developers is a massive reduction in boilerplate pipeline configuration. If you are shipping a modern Windows desktop app or an indie game, handling multiple hardware architectures usually requires separate repository branches or complex shell scripts.

With v0.3.2, your build system can compile individual x64 and ARM64 binaries locally or in a CI agent, and then instantly wrap them together. The output generates an unsigned bundle ready for the Microsoft Store (which signs it on your behalf) or local signing via winapp sign for independent sideloading.

Furthermore, the automation improvements mean your CI terminals (like GitHub Actions or Azure DevOps) will no longer break due to interactive shell crashes. The tool automatically swaps out animated loaders for append-only text strings when it detects a non-interactive environment.

Our Analysis

Our stance on this update is highly positive; it is exactly what the modern Windows desktop ecosystem needs to stay relevant to cross-platform engineers. For a long time, cross-platform developers using frameworks like Flutter, Tauri, or Rust felt like second-class citizens in the Windows ecosystem due to Visual Studio-centric tooling. By advancing a unified, framework-agnostic CLI, Microsoft is finally decoupling app deployment from heavy IDEs.

We predict that this will accelerate the adoption of ARM64 targeting for desktop software. Developers frequently skip building for ARM64 simply because setting up a secondary distribution package is annoying. This single-command packaging removes that excuse entirely.

Compared to older iterations of Windows deployment-where devs had to manually configure complex .wxs WiX files or deal with massive, rigid MSBuild configurations-the WinApp CLI feels lightweight and modern. It brings the developer experience closer to the modern web tooling ecosystem (like Vite or Cargo) that builders actually enjoy using.

Here is how to compile your multi-architecture binaries and bundle them together using the new CLI workflow:

# Step 1: Compile the release build for x64 architecture
dotnet publish -c Release -r win-x64 --self-contained false -o publish/x64

# Step 2: Compile the release build for ARM64 architecture
dotnet publish -c Release -r win-arm64 --self-contained false -o publish/arm64

# Step 3: Bundle both architectures into a single production-ready package
winapp pack publish/x64 publish/arm64

FAQs

Q: Does the new MSIX bundle format sign my application automatically?

A: No, the command outputs an unsigned bundle. If you are uploading directly to the Microsoft Store, you can submit it as-is because Microsoft signs it for you. If you plan on distributing the app via sideloading, you will need to run winapp sign afterward.

Q: Can I use the smart initialization command inside a monorepo framework?

A: Yes. If you run winapp init at the root of a multi-project directory, it will detect all compatible instances (such as Rust, .NET, or Electron) and prompt you with a menu to select the specific project you want to initialize.

Q: Will the update checks disrupt my automated build scripts?

A: No, the tool handles this gracefully. It only checks for updates once per day on the first command run, and it features an automatic timeout mechanism to ensure network issues never hang your build pipeline.

Q: How do I upgrade my local installation to version 0.3.2?

A: You can pull the latest update via WinGet by executing winget install Microsoft.WinAppCLI or update it locally using npm if you manage it as a project dev dependency.

Our Take

Windows App Development CLI v0.3.2 removes the structural friction of targeting multiple architectures. By treating command-line automation and cross-framework support as top-tier features, Microsoft is moving in a direction that respects the real-world toolchains of indie builders and enterprise engineers alike. We will continue monitoring the tool's public preview performance as it marches toward a stable 1.0 milestone.