avalonia-custom-controls

Choose UserControl for simple XAML composition and TemplatedControl when you need clear styling boundaries and template overriding. This Avalonia control design guidance maps reuse goals to the correct base class for your application architecture.

Use StyledProperty for standard dependency properties supporting styling and data binding, and DirectProperty for lightweight wrappers around plain C# properties. This pattern ensures correct property ownership and system integration in Avalonia custom controls.

AttachedProperty allows defining properties on a parent class for use by child elements in XAML. This guidance covers implementing attached properties and applying them to enable flexible layout and behavior configuration across control libraries.

Structure your Avalonia control library by embedding themes directly within the project. This approach provides clear distribution strategies and ensures consumers receive properly themed templated controls without external style dependencies.

Override the Render method within a base Control class to perform low-level custom drawing operations. This technique bypasses standard templating to achieve precise visual rendering for specialized Avalonia UI requirements.

Yes, this guidance details common pitfalls and best practices regarding property systems, inheritance, and rendering. It helps avoid styling boundary leaks and ensures robust library distribution for reusable Avalonia controls.