{"id":1181,"date":"2026-06-11T10:16:12","date_gmt":"2026-06-11T17:16:12","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/ifdef-windows\/?p=1181"},"modified":"2026-06-11T10:16:12","modified_gmt":"2026-06-11T17:16:12","slug":"windows-app-development-cli-v0-3-2-bundling-support-smarter-initialization-and-more","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/ifdef-windows\/windows-app-development-cli-v0-3-2-bundling-support-smarter-initialization-and-more\/","title":{"rendered":"Windows App Development CLI v0.3.2 \u2014 bundling support, smarter initialization, and more"},"content":{"rendered":"

\"blog<\/a><\/p>\n

Windows App Development CLI v0.3.2 is here! This release brings MSIX bundle support for multi-architecture packaging, a smarter winapp init<\/code> experience that auto-detects your projects, higher quality UI screenshots, and a handful of reliability fixes across the board. Get the update by running winget install Microsoft.WinAppCLI<\/code> or check the repo for other install options<\/a>.<\/p>\n

Get started with the Windows App Development CLI<\/a><\/div><\/p>\n

Let’s take a look at what’s new.<\/p>\n

\ud83d\udce6 MSIX Bundle Support<\/h2>\n
\n

The pack<\/code> command now supports creating MSIX bundles \u2014 multi-architecture packages that combine x64 and ARM64 builds into a single .msixbundle<\/em> file. This is the format the Microsoft Store expects for multi-arch submissions, and it’s now a single command away.<\/p>\n<\/div>\n

\n
# Build for both architectures\r\ndotnet build -c Release -r win-x64 -o publish\/x64\r\ndotnet build -c Release -r win-arm64 -o publish\/arm64\r\n\r\n# Bundle them together\r\nwinapp pack publish\/x64 publish\/arm6<\/code><\/pre>\n
That’s it. WinApp CLI detects the architectures from each folder, packages them individually, and wraps them into a bundle. The output is a ready-to-upload .msixbundle<\/em> \u2014 unsigned for Store submissions (where Microsoft signs on your behalf) or ready for winapp sign<\/code> if you’re sideloading.<\/p>\n<\/div>\n
\"Bundling<\/a><\/p>\n
\ud83e\udde0 Smarter Initialization<\/h2>\n
The init<\/code> command got a significant upgrade in how it discovers and configures projects. Run it in a directory with multiple project types and it now detects compatible projects and presents a clean selection menu:<\/p>\n
\"Init<\/a><\/p>\n
The command also now warns you when you’re running in an incompatible directory (like the root of a monorepo) and places configuration files in the right location relative to your project file. For CI and scripting, –use-defaults<\/em> skips all prompts and applies sensible defaults automatically. We also fixed a crash that occurred when running winapp init<\/code> in non-interactive shells \u2014 it now falls back to default behavior gracefully.<\/p>\n
\n
\ud83d\udcf8 Higher Quality UI Screenshots<\/h2>\n
The winapp ui screenshot<\/code> command now produces higher quality captures that preserve rounded window corners and don’t include any black border. We’ve also added a –focus<\/em> flag that brings the target window to the foreground before capturing.<\/p>\n
# Capture a high-quality screenshot of a specific window\r\n\r\nwinapp ui screenshot --process MyApp --focus<\/code><\/pre>\n
<\/div>\n
\u26a1 Other Notable Changes<\/h2>\n