Live Avalonia topology
Runtime Trees
Turn the running interface into explicit, queryable structure.
Explore source ↗Capability
Inspector enumerates both visual and logical Avalonia trees with stable node identities, hierarchy, type, name, classes, bounds, visibility, and schema-aware metadata.
- 01
Visual and logical tree snapshots
- 02
Stable node identifiers
- 03
Type, name, classes, bounds, and visibility
- 04
Portable contracts for custom clients
How it composes
From intent
to working system.
Connect
A host or process target creates a reusable Inspector session.
Traverse
Avalonia adapters walk visual or logical children from the active root.
Normalize
Runtime controls become stable node DTOs with portable metadata.
Query
CLI and custom clients retrieve complete trees as text or deterministic JSON.
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 add package Inspector.AvaloniaAdapterdotnet add package Inspector.Contracts<PackageReference Include="Inspector.AvaloniaAdapter" Version="VERSION" /><PackageVersion Include="Inspector.AvaloniaAdapter" Version="VERSION" />inspector connect --mode process --pid 12345 --json# Capture data.sessionId from the response.inspector tree get --session-id sess-123 --kind visual --jsoninspector tree get --session-id sess-123 --kind logical --jsonModules 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.