This page focuses on the packaged VS Code extension workflow.
Usually this means VS Code persisted the old view location from a previous build.
Try:
View: Reset View LocationsAXSG Inspector: Show Inspector PanelThe intended layout is:
Check:
.xaml or .axaml so AXSG activatesIf you just rebuilt the VSIX locally, reinstall that exact package and reload the window.
Start with the AXSG Language Server output channel.
Common causes:
axsg.preview.hostProject is not setRecommended settings while diagnosing:
{
"axsg.preview.compilerMode": "auto",
"axsg.preview.buildBeforeLaunch": true
}
In auto mode this should fall back cleanly to Avalonia/XamlX.
If you forced:
{
"axsg.preview.compilerMode": "sourceGenerated"
}
then the preview will fail until the AXSG runtime output is present in the build output.
Set:
{
"axsg.preview.hostProject": "/path/to/your/app.csproj"
}
Optionally also set:
{
"axsg.preview.targetFramework": "net10.0"
}
if the project multi-targets and the chosen desktop TFM is not the one you want.
Check the workspace mode in the preview toolbar:
Interactive for normal app inputDesign for hit testing and overlay selectionIf clicks are selecting elements instead of pressing buttons, you are in Design.
If keyboard input is not reaching the previewed app, confirm you are not in Design.
Try:
AXSG Inspector: RefreshDocumentsAlso verify that the active editor is the same XAML document that belongs to the active preview session.
The runtime mutation pipeline operates against the current active design document and selected element.
Before editing:
DocumentsLogical Tree or Visual Tree to verify the current selectionThe packaged extension bundles designer-host native assets for:
If preview startup still reports missing native rendering libraries, the installed VSIX is usually stale or incomplete. Reinstall the freshly packaged extension and reload VS Code.