microsoft / microsoft/react-native-windows
Remove load guard once WinUI 3 and system XAML can coexist
Open
Nobody has claimed this yet.
Area: WinUI
enhancement
Needs WinUI 3
Platform: WinAppSDK
Workstream: Module Support
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
At some point it may be possible to use WinUI 3 and system XAML in the same process. Today that's not supported and we can end up in hard to debug states, so we have a load guard that will crash if we try to load incompatible DLLs.
Once we can load both, we should remove the load guard.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the load guard responsible for preventing WinUI 3 and system XAML from loading together, then review how the incompatible DLL state is detected. Confirm that both technologies can coexist in one process before removing the guard and verify that the existing failure protection is no longer needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop, operating-systems
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100