[docs] Document unpackaged WinUI 3 debugging fix in VS Code extension

[aspire-repo-bot]

Documents changes from microsoft/aspire#19877

@ellahathaway

Targeting release/13.6 based on the source PR milestone 13.6.

Why

microsoft/aspire#19877 fixes a crash (0xC000027B in Microsoft.UI.Xaml.Application.Start()) when debugging unpackaged WinUI 3 projects through the Aspire VS Code extension. The PR body includes a "User-facing usage" section explaining that the extension now launches the generated apphost executable (RunCommand) instead of the managed DLL, with no project configuration changes required. This is a user-visible behavior change to the existing debugging experience described on the VS Code extension docs page, so it needed to be captured there.

What changed

• Added a note under Language coverage in src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx explaining that unpackaged WinUI 3 resources (added via a normal Project launch profile, e.g. builder.AddProject<Projects.WinUIApp>("winui")) are launched via their generated apphost executable rather than the managed DLL, and that no project configuration changes, debugger attach behavior, launch-profile arguments, environment variables, or cleanup behavior are affected.

Files modified

• src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx (updated existing page, no new pages created)

Generated by PR Documentation Check for #19877 · auto · 38.8 AIC · ⌖ 8.27 AIC · ⊞ 19.7K · ◷

[aspire-repo-bot]

Frontend HTML artifact ready

The latest frontend build uploaded the frontend-dist artifact for PR #1616. Use the VS Code button below to open this PR with GitHub Artifacts Explorer and browse the built HTML locally.

This comment updates automatically when a new frontend build artifact is uploaded.