Language Service and Tooling Namespaces

This namespace family covers editor semantics, LSP request handling, projected inline-code support, and the tooling surface shared by the VS Code extension and in-app editors.

Packages behind this area

XamlToCSharpGenerator.LanguageService
XamlToCSharpGenerator.LanguageServer.Tool
XamlToCSharpGenerator.RemoteProtocol
XamlToCSharpGenerator.McpServer.Tool
VS Code extension
XamlToCSharpGenerator.Editor.Avalonia

Primary namespaces

What lives here

Shared semantic engine

The LanguageService namespaces own completion, hover, navigation, references, rename, semantic highlighting, inlay hints, and cross-file reference analysis.

Inline-code tooling

LanguageService.InlineCode and related navigation/completion services analyze inline C# snippets and can project them into temporary C# documents when editor-side interoperability is useful.

Server transport and protocol

LanguageServer contains the standalone LSP host, request routing, and metadata virtual-document support. Shared framing and remote contracts now live in RemoteProtocol.

MCP and shared remote contracts

RemoteProtocol, McpServer.Tool, and PreviewerHost cover the MCP-facing surface for workspace queries, preview orchestration, preview hot reload, and runtime-hosted resource subscriptions.

In-process editor hosting

Editor.Avalonia wraps the semantic engine for AvaloniaEdit-based in-app editor scenarios.

Use this area when

you are debugging completion, definitions, references, or rename behavior
you are extending VS Code integration or another editor host
you are profiling startup, workspace load, or cross-file reference performance
you are working on inline-C# editing support

Suggested API entry points

The concrete server host AxsgLanguageServer is intentionally internal. Treat the package guide as the supported documentation surface for that host.