wpf-to-avalonia

Port WPF applications and patterns to Avalonia, including dependency-property mapping, bindings, resources, templates, layout, rendering, and shell behavior. Use for `DependencyProperty`, routed-command, trigger, `Frame` or `Page`, `OnRender`, `HwndHost`, or other WPF-to-Avalonia migration work.

Stars 57

Forks 6

Install this agent skill to your Project

npx add-skill https://github.com/wieslawsoltes/development-plugin-for-avalonia/tree/main/skills/wpf-to-avalonia

SKILL.md

WPF to Avalonia

Start with:

../../references/64-wpf-to-avalonia-modern-ui-conversion-index.md
../../references/wpf-to-avalonia/README.md

Prioritize the chapters that match the WPF source:

property system, bindings, resources, styles, and templates
layout, navigation, windows, dialogs, and dispatcher workflows
rendering, animation, popup, interop, and document workflows
advanced control families, selection models, and platform services

Workflow

Map the WPF concept first, then choose the Avalonia equivalent or redesign.
Call out where Avalonia does not preserve a WPF subsystem directly, especially triggers, navigation, and interop.
Replace resource, layout, and rendering assumptions before doing control-by-control cleanup.
Keep the migration narrative explicit about what stays familiar and what changes materially.

Rules

Do not promise WPF trigger, CommandManager, or HwndHost parity where it does not exist.
Use Avalonia selectors, templates, and state patterns rather than recreating WPF internals.
Keep document and printing workflows in a separate explicit decision track.