[DO NOT MERGE] 0.3 Blog Draft#480
Conversation
Build Metrics ReportBinary Sizes
Test Results✅ 783 passed, 1 skipped out of 784 tests in 449.2s (-20.3s vs. baseline) Test Coverage❌ 21.5% line coverage, 36.6% branch coverage · ✅ no change vs. baseline CLI Startup Time45ms median (x64, Updated 2026-04-22 16:36:40 UTC · commit |
Co-authored-by: Nikola Metulev <nmetulev@users.noreply.github.com>
…into cm/0.3-blog
|
|
||
| And for **.NET developers** in particular, this release makes things even smoother with a new NuGet package that brings `dotnet run` support for packaged apps right out of the box. | ||
|
|
||
| Get the update by running `winget install Microsoft.WinAppCLI` or [check the repo for other install options](https://github.com/microsoft/winappCli). |
There was a problem hiding this comment.
There seems to be some inconsistency in how the package name is referenced across the project. I’ve seen at least three variations:
-
Microsoft.WinAppCLI
-
Microsoft.WinAppCli
-
Microsoft.winappcli
It might be worth standardizing on a single form to avoid confusion for contributors and users.
Jaylyn-Barbee
left a comment
There was a problem hiding this comment.
Nothing that has to be changed just some nits and suggestions. Nice work overall!
| - **`--unregister-on-exit`**: Automatically cleans up the registered package when the app closes. Perfect for clean test runs where you don't want leftover state. | ||
| - **`--debug-output`**: Captures `OutputDebugString` messages and exceptions in real time. When a crash occurs, a minidump is automatically captured and analyzed in-process. Managed (.NET) crashes are triaged via ClrMD; native (C++/WinRT) crashes are analyzed via DbgEng. Add `--symbols` to download PDBs from the Microsoft Symbol Server for full function names in native stacks. | ||
|
|
||
| Whether you're a developer iterating locally or an agent running end-to-end validation, `winapp run` gives you a single command to go from build output to a running, debuggable packaged app. |
There was a problem hiding this comment.
| Whether you're a developer iterating locally or an agent running end-to-end validation, `winapp run` gives you a single command to go from build output to a running, debuggable packaged app. | |
| Whether you're a developer iterating locally or using an agent to run end-to-end validation, `winapp run` gives you a single command to go from build output to a running, debuggable packaged app. |
I only call this out because it's going to be a human reading this blog post, right?
Blog Draft for v0.3 WinAppCLI release. Creating PR as a spot for comments.