Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
aspire-repo-bot wants to merge 1 commit into
base: release/13.6
Choose a base branch
from
Draft

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

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -197,6 +197,10 @@ The extension detects each resource's language and attaches the right debugger:
| C# / .NET | `coreclr` | [C# Dev Kit](https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.csdevkit) (recommended) or [C#](https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.csharp) |
| Azure Functions | Per language | [Azure Functions](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azurefunctions) plus the language extension for your function app (C#, JavaScript/TypeScript, or Python) |

::::note[Unpackaged WinUI 3 projects]
For an unpackaged WinUI 3 resource added with a normal `Project` launch profile (for example, `builder.AddProject<Projects.WinUIApp>("winui")`), the extension launches the project's generated apphost executable (`RunCommand`) instead of the managed DLL. Launching the managed DLL directly under the debugger crashes WinUI 3 startup in `Microsoft.UI.Xaml.Application.Start()`. No project configuration changes are required — debugger attach, launch-profile arguments, environment variables, and cleanup behavior are unaffected.
::::

## Feedback and issues

Found a bug or have an idea? File it on the [microsoft/aspire](https://github.com/microsoft/aspire/issues) repo:
Expand Down
Loading