No,Category,Guideline,Description,Do,Don't,Code Good,Code Bad,Severity,Docs URL 1,XAML,Use Avalonia XAML namespace,Avalonia has its own XAML namespace not WPF,xmlns= for Avalonia-specific namespace,WPF xmlns or UWP xmlns,"","",High,https://docs.avaloniaui.net/docs/fundamentals/avalonia-xaml 2,XAML,Use compiled bindings with x:DataType,Enable compile-time binding validation,x:DataType on root or DataTemplate for compiled bindings,Reflection-based bindings in production,""," without x:DataType",High,https://docs.avaloniaui.net/docs/data-binding/compiled-bindings 3,XAML,Enable compiled bindings globally,AvaloniaUseCompiledBindingsByDefault in csproj makes every binding require x:DataType and is required for trim-safe Native AOT,AvaloniaUseCompiledBindingsByDefault MSBuild property in csproj,Relying on runtime binding resolution,"true","No compiled binding enforcement",High,https://docs.avaloniaui.net/docs/data-binding/compiled-bindings 4,XAML,Use #name shorthand for element-to-element bindings,Compiled bindings cannot resolve {Binding ElementName=...} - use the #name shorthand which relies on NameScope lookup,#name shorthand referencing x:Name controls in the same NameScope,ElementName binding inside a compiled-binding scope,""," under compiled bindings",Medium,https://docs.avaloniaui.net/docs/data-binding/compiled-bindings 5,Styling,Use CSS-like selectors,Avalonia uses selectors not implicit styles,Selectors targeting control types classes and pseudoclasses,WPF-style implicit Style with TargetType,"",""," for hover effects",Medium,https://docs.avaloniaui.net/docs/styling/pseudoclasses 7,Styling,Use nesting selectors,Child and descendant combinators for scoped styles,> for direct child and space for descendant,Flat selectors that match too broadly,"","