One semantic engine, many editors
Language & Preview Tooling
Keep authoring behavior consistent from VS Code to an in-app XAML editor.
Explore source ↗Capability
Completion, diagnostics, definitions, references, hover, inlay hints, rename, semantic highlighting, inline C# intelligence, and Avalonia preview power a VS Code extension, LSP tool, and embeddable editor control.
- 01
Completion, diagnostics, navigation, and rename
- 02
Inline C# semantic tooling
- 03
VS Code and reusable Avalonia editor
- 04
Source-generated and XamlX preview modes
How it composes
From intent
to working system.
Workspace
Projects, documents, references, and generated context establish semantics.
Analyze
Shared services answer XAML and inline C# language queries.
Protocol
LSP carries editor-neutral requests and diagnostics.
Preview
A managed host renders saved or live source-generated markup.
Quick start
Adopt this
capability.
Start with the primary module, then add the related packages only when the application needs those layers. Replace VERSION with the current NuGet version.
dotnet tool install --global XamlToCSharpGenerator.LanguageServer.Tooldotnet tool install --global XamlToCSharpGenerator.LanguageServer.Toolaxsg-lsp
# VS Code releases also include the AXSG extension# with source-generated live preview.Modules in this capability
Use one layer.
Compose the rest.
Source of truth
Read the module beside the complete system.
The implementation, samples, issues, and release notes stay in the parent repository so module details remain connected to the product architecture.