Note
Kailangan ng pahintulot para ma-access ang page na ito. Maaari mong subukang mag-sign in o magpalit ng mga direktoryo.
Ang pag-access sa pahinang ito ay nangangailangan ng pahintulot. Maaari mong subukang baguhin ang mga direktoryo.
WinUI 3 and the Windows App SDK are the modern foundation for Windows apps. AI tools can automate much of the mechanical migration work — namespace substitutions, API replacements, project file updates — but they need accurate guidance to avoid reproducing outdated patterns.
The main risk is drift toward older stacks. AI models have more training data for UWP and WPF than for WinUI 3, so provide exact API mappings when prompting for migration code.
Choose your migration path
| From | To | AI skill | Guide |
|---|---|---|---|
| WPF (.NET) | WinUI 3 | winui-wpf-migration |
Migrate from WPF |
| UWP | WinUI 3 | — | Migrate from UWP |
| iOS / SwiftUI | WinUI 3 | — | Migrate from iOS |
| React Native / Electron / MAUI / Flutter | WinUI 3 | — | Cross-framework considerations |
Before you start
- Work in a branch before running large AI-assisted rewrites.
- Verify your dependencies support .NET 10 and Windows App SDK packaging.
- Review the Windows App SDK migration guide.
- Prepare API mapping tables before prompting — the per-framework pages have them ready to paste.
Related content
Makipagtulungan sa amin sa GitHub
Ang pinagmulan para sa content na ito ay mahahanap sa GitHub, kung saan maaari ka ring lumikha at sumuri ng mga isyu at mga pull request. Para sa higit pang impormasyon, tingnan ang aming gabay sa contributor.
Windows developer