AXSG ships multiple artifacts because the project spans compile-time, runtime, editor, and release tooling.
Use these first unless you are composing a custom toolchain:
| Artifact | Kind | Install |
|---|---|---|
XamlToCSharpGenerator |
Application NuGet package | dotnet add package XamlToCSharpGenerator |
XamlToCSharpGenerator.LanguageServer.Tool |
.NET tool package | dotnet tool install --global XamlToCSharpGenerator.LanguageServer.Tool |
XamlToCSharpGenerator.McpServer.Tool |
.NET tool package | dotnet tool install --global XamlToCSharpGenerator.McpServer.Tool |
AXSG XAML Language Service |
VS Code extension | code --install-extension ./axsg-language-server-x.y.z.vsix |
For custom compiler, runtime, or tooling integration, AXSG also ships:
XamlToCSharpGenerator.BuildXamlToCSharpGenerator.RuntimeXamlToCSharpGenerator.Runtime.CoreXamlToCSharpGenerator.Runtime.AvaloniaXamlToCSharpGenerator.RemoteProtocolXamlToCSharpGenerator.LanguageServiceXamlToCSharpGenerator.Editor.AvaloniaXamlToCSharpGenerator.GeneratorXamlToCSharpGenerator.CoreXamlToCSharpGenerator.CompilerXamlToCSharpGenerator.Framework.AbstractionsXamlToCSharpGenerator.ExpressionSemanticsXamlToCSharpGenerator.MiniLanguageParsingXamlToCSharpGenerator.AvaloniaXamlToCSharpGenerator.NoUiOperational host artifacts that are important but not shipped as standalone packages include:
XamlToCSharpGenerator.PreviewerHostXamlToCSharpGenerator.Previewer.DesignerHostUse Artifact: XamlToCSharpGenerator.PreviewerHost when the system you need to control is preview itself.
For the full current matrix with badges and marketplace links, see the repository README.
For the docs-specific mapping between package identity, shipped payload, and generated API coverage, see Package and Assembly.