winui-wpf-migration Skill
Migrate WPF applications to WinUI 3 — namespace replacement (System.Windows → Microsoft.UI.Xaml), control mapping (DataGrid→ListView, WrapPanel→ItemsRepeater, TabControl→TabView), threading (Dispatcher→DispatcherQueue), imaging (System.Drawing→BitmapImage), MVVM conversion to CommunityToolkit.Mvvm, and DynamicResource→ Published by microsoft in win-dev-skills.
What is winui-wpf-migration Skill?
Migrate WPF applications to WinUI 3 — namespace replacement (System.Windows → Microsoft.UI.Xaml), control mapping (DataGrid→ListView, WrapPanel→ItemsRepeater, TabControl→TabView), threading (Dispatcher→DispatcherQueue), imaging (System.Drawing→BitmapImage), MVVM conversion to CommunityToolkit.Mvvm, and DynamicResource→ Published by microsoft in win-dev-skills. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Security review
- Data analysis
- Design and media
- Writing
- Security review use cases
Technical details
- Install or run with Copy skill directory
When to use winui-wpf-migration Skill
- Use it for security review.
- Use it for data analysis.
- Use it for design and media.
- Use it for writing.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/win-dev-skills
- Skill file: plugins/winui/skills/winui-wpf-migration/SKILL.md
What it does
Migrate WPF applications to WinUI 3 — namespace replacement (System.Windows → Microsoft.UI.Xaml), control mapping (DataGrid→ListView, WrapPanel→ItemsRepeater, TabControl→TabView), threading (Dispatcher→DispatcherQueue), imaging (System.Drawing→BitmapImage), MVVM conversion to CommunityToolkit.Mvvm, and DynamicResource→
Skill instructions
Migration Process Step 1: Audit the WPF Source Before writing code, inventory WPF-specific APIs: powershell Find all WPF namespace usage Select-String -Path (Get-ChildItem -Recurse -Filter ".cs" | Where-Object { $.FullName -notlike "\obj" }) -Pattern "System.Windows." | Select-Object -Property Filename, LineNumber, Line List: WPF controls used, custom MVVM framework, imaging APIs, threading patterns, Win32 interop. Step 2: Create WinUI 3 Project and Align Namespaces powershell dotnet new winui-mvvm -n <AppName Immediately set <RootNamespace in .csproj to match the WPF namespace. Update x:Class in App.xaml, MainWindow.xaml and their code-behind files. Build to verify before porting any code. Step 3: Replace Namespaces | WPF | WinUI 3 | |-----|---------| | System.Windows | Microsoft.UI.Xaml | | System.Windows.Controls | Microsoft.UI.Xaml.Controls | | System.Windows.Media | Microsoft.UI.Xaml.Media | | System.Windows.Input | Microsoft.UI.Xaml.Input | | System.Windows.Data | Microsoft.UI
Explore related resources
Frequently asked questions
What is winui-wpf-migration?
winui-wpf-migration is a open-source AI agent skill with Copy skill directory. Migrate WPF applications to WinUI 3 — namespace replacement (System.Windows → Microsoft.UI.Xaml), control mapping (DataGrid→ListView, WrapPanel→ItemsRepeater, TabControl→TabView), threading.
Who is winui-wpf-migration best for?
winui-wpf-migration is best for reusing agent instructions, scripts, and references, security review workflows, data analysis workflows, design and media workflows.
How do I install winui-wpf-migration?
Install or run winui-wpf-migration using Copy skill directory. Check winui-wpf-migration for the latest setup command.
Is winui-wpf-migration actively maintained?
winui-wpf-migration may need a closer maintenance check before production use.
Auto-fetched from GitHub.
