RNW supports WinAppSDK – Phase 3 “Stable” #9393
Description
Building on top of #9601, this issue tracks the set of sub-issues that are required before RNW support for WinAppSDK is said to be Stable.
Original project board: Re-target onto Windows App SDK
Spec (Internal link)
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" : active, phase3, after phase2, 40d
9139 : phase3f, after phase2, 15d
9602 : phase3e, after phase3f, 2d
9137 : phase3b, after phase3e, 5d
9144 : phase3c, after phase3b, 15d
9112 : phase3d, after phase2, 5d
8133 : phase3h, after phase3d, 5d
5305 : phase3i, after phase3h, 5d
5474 : phase3k, after phase3i, 5d
8312 : phase3j, after phase3k, 5d
Phase 4 "Default" : phase4, after phase3, 26d
Phase 3 "Stable"
- WinAppSDK support for creating modules with CLI #9139
- Update usage docs for how to create modules for WinAppSDK #9602
- Trying to use modules/apps across UWP/WinAppSDK should provide a meaningful error message #9137
- Create e2etestapp for WinAppSDK #9144
- Allow --useWinUI3 and --experimentalNugetDependency to be used together in CLI #9112 (may have significant impact on cost if we don't support source right away)
- Remove WinUI 3 preview support from UWP templates and CLI #8133
- WinUI3: No UIContext property for SIP #5305
- Remove usage of DisplayInformation GetForCurrentView #5474
- Enable WarnAsError for ProjectReunion #8312
Bugs
Bugs to fix before completion