Native UI inspection
Framework Adapters
Inspect native XAML applications with browser-grade tooling concepts.
Explore source ↗Capability
Avalonia, Uno Platform, WPF, and WinUI adapters map visual trees, properties, styles, input, screenshots, and runtime state into CDP domains.
- 01
Avalonia visual and logical trees
- 02
Uno, WPF, and WinUI adapters
- 03
Property and style inspection
- 04
Input, overlays, and screenshots
How it composes
From intent
to working system.
Tree
Native elements receive stable protocol identities and hierarchy.
Property
Framework properties, bindings, styles, and resources map to inspectable data.
Action
Input, highlighting, edits, and captures call native services.
Protocol
Results return through standard CDP commands and events.
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 Chrome.DevTools.Avalonia --prerelease<PackageReference Include="Chrome.DevTools.Avalonia" Version="VERSION" /><PackageVersion Include="Chrome.DevTools.Avalonia" Version="VERSION" />AppBuilder.Configure<App>() .UsePlatformDetect() .UseCdpDiagnostics(options => options.Port = 9222);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.