Developing a component
A component directory contains one packable project under src/. Keep its public XAML examples in
samples/, its manual reproduction window in dev/, and its automated checks in tests/.
Open the component’s dev app directly when debugging keyboard focus, flyout positioning, or a specific interaction.
The gallery references the sample library. A sample library references the component through its public API.
component.props owns the package ID, version, display name, release stage, documentation slug, and verification entry points.
Run ./eng/Get-Components.ps1 -Json from the library checkout to inspect the catalog used by release automation and this site.
For Searchable Flyouts, run ./eng/Build.ps1 -TestPackage on Windows to test both .NET targets,
pack the library, and publish a clean consumer with Native AOT. The component’s accessibility and release notes record the remaining manual checks.