wpf

# WPF ## Trigger On - working on WPF UI, MVVM, binding, commands, or desktop modernization - migrating WPF from .NET Framework to .NET - integrating newer Windows capabilities into a WPF app - implementing data binding, styles, templates, or control customization ## Documentation - [WPF Overview](https://learn.microsoft.com/en-us/dotnet/desktop/wpf/overview/) - [Data Binding Overview](https://learn.microsoft.com/en-us/dotnet/desktop/wpf/data/) - [MVVM Toolkit Introduction](https://learn.microsoft.com/en-us/dotnet/communitytoolkit/mvvm/) - [Styles and Templates](https://learn.microsoft.com/en-us/dotnet/desktop/wpf/controls/styles-templates-overview) - [Migration Guide](https://learn.microsoft.com/en-us/dotnet/desktop/wpf/migration/) ### References - [patterns.md](references/patterns.md) - MVVM patterns, binding patterns, command patterns, and reusable architectural approaches - [anti-patterns.md](references/anti-patterns.md) - Common WPF mistakes and how to avoid them ## Workflow 1. **Confirm Windows-only scope** — WPF is Windows-only even when the wider .NET stack is cross-platform 2. **Apply MVVM pattern** — keep views dumb, logic in ViewModels, use commands 3. **Manage data binding explicitly** — choose correct binding modes, validate at runtime 4. **Use styles and templates deliberately** — keep UI composable, avoid page-specific hacks 5. **Handle threading correctly** — use Dispatcher for UI updates, async/await for long operations 6. **Validate both designer and ...