wpf-to-uno-migration

Migrate WPF project code to Uno Platform with phased patterns.

5|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/mtmattei/UnoPlatformSkills --skill wpf-to-uno-migration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wpf-to-uno-migration
Source: https://github.com/mtmattei/UnoPlatformSkills/tree/main/wpf-to-uno-migration
Command: npx skills add https://github.com/mtmattei/UnoPlatformSkills --skill wpf-to-uno-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Migrating WPF applications to Uno Platform is error-prone due to pattern mismatches in navigation, theming, and platform-specific services; this skill provides a structured, patterns-based approach to porting with minimal risk.

Core Features & Use Cases

  • Guided migration patterns from WPF to Uno, including NavigationView/frame patterns, ContentDialog conversions, and DI-based settings.
  • Preserves feature parity while reducing cross-platform issues.
  • Use cases: planning a migration, executing incremental port, debugging blank pages from resource keys.

Quick Start

Start by scaffolding a Uno Platform shell and port a representative WPF page to a Uno Page using MVUX and NavigationView.

Frequently Asked Questions about wpf-to-uno-migration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate WPF to Uno Platform without breaking navigation and theming?

Migrating WPF to Uno Platform requires a phased, patterns-based approach to map namespaces, convert navigation to NavigationView, align Material theme resources, and configure DI. This structured porting strategy minimizes cross-platform issues and preserves feature parity.

What is the best way to convert WPF ContentDialog patterns to Uno Platform?

Converting WPF ContentDialog patterns to Uno Platform involves applying explicit API mapping and utilizing MVUX-based state management. This ensures cross-platform dialog compatibility while maintaining the original application's feature parity.

Why does my migrated Uno Platform page render blank after porting from WPF?

Blank pages during WPF to Uno migration often occur when Material theme resource keys lack alignment or namespace mapping is incorrect. Debugging requires verifying explicit namespace/API mapping and ensuring proper MVUX state management integration.

Can I use MVUX state management when porting desktop WPF applications to cross-platform Uno?

Yes, porting desktop WPF applications to cross-platform Uno supports MVUX-based state management. The migration workflow integrates MVUX alongside Dependency Injection setup and NavigationView frame routing to preserve application state across platforms.

Do I need to scaffold a new Uno Platform shell before porting WPF pages?

Yes, scaffolding a Uno Platform shell is the required starting point for WPF to Uno migration. You then port a representative WPF page to a Uno Page using MVUX and NavigationView to establish the cross-platform routing structure.

Does WPF to Uno migration support Dependency Injection setup for platform-specific services?

Yes, WPF to Uno migration explicitly supports DI-based settings for platform-specific services. The phased migration workflow maps WPF service patterns to Uno's Dependency Injection framework, ensuring proper cross-platform service resolution.