RNW supports WinAppSDK – Phase 4 “Default” #9394
Description
Building on top of general support for WinAppSDK, this issue tracks the set of sub-issues that are required before RNW would change the default from UWP to WinAppSDK.
It's expected that as part of this UWP support still exists in parallel, but is not the default option for new projects.
Phase 0 | Phase 1 | Phase 2 | Phase 3 | Phase 4
Estimated Schedule
gantt
section WinAppSDK
Phase 0 "Prototype" :done, phase0, 2022-01-01, 2022-03-21
Phase 1 "Experimental" :done, phase1, 2022-03-28, 53d
Phase 2 "Preview": done, phase2, after phase1, 22d
Phase 3 "Stable" : done, phase3, after phase2, 40d
Phase 4 "Default" : active, phase4, after phase3, 26d
9140 : phase4a, after phase3, 5d
9138 : phase4b, after phase4a, 5d
9590 : phase4c, after phase4b, 5d
4305 : phase4e, after phase4c, 5d
9197 : phase4f, after phase3, 5d
9546 : phase4g, after phase4f, 5d
9135 : phase4d, after phase4g, 5d
9711 : phase4h, after phase4d, 5d
Phase 4 "Default"
- Upgrade RNGallery to WinAppSDK or create fork #9140
- C# WinAppSDK app should use single project #9138
- Port WebView module to WinUI3 #9590
- Use UIElement focus #4305
- Start Marking Windows App SDK dim-down features #9197
- Improve/simplify process on aligning XAML/WinUI version #9546
- Clean up bifurcation based on old winui3 / islands code #9135 (Engineering efficiency (internal-facing) to reduce our test matrix and make us more agile)
- Rename / Rethink project creation flags for WinAppSDK #9711