you want to embed an AXAML editor inside an Avalonia application
you need AXSG completion, semantic tokens, or navigation in-process
you want editor behavior backed by the same language-service engine used by the standalone server
What it adds
This package layers:
an AvaloniaEdit-based editor host
AXSG language-service integration
document/update plumbing suitable for in-app editing surfaces
editor-facing abstractions over syntax highlighting, diagnostics, and semantic updates
It is intended for product-quality editor surfaces, not just sample or test usage.
Typical use cases
Use this package when you are building:
an in-app AXAML editor
a design tool that needs editing plus semantic services
a desktop workflow where the language service must run in-process
Dependency shape
This package sits on top of:
XamlToCSharpGenerator.LanguageService
Avalonia
Avalonia.AvaloniaEdit
That means it is best suited for in-process editor experiences inside AXSG-aware desktop tools or product shells.
What it does not replace
If you only need the semantic engine, use XamlToCSharpGenerator.LanguageService directly. If you need an out-of-process LSP server, use XamlToCSharpGenerator.LanguageServer.Tool.