You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the MSIX packaging project, if both UWP and WinUI 3 desktop applications are used, and UWP references WinUI 2, after compiling and deploying to the local device, Since both WinUI 2 and WinUI 3 use Microsoft.UI.Xaml.dll, application startup dependency lookup issues can occur. Specifically, the order of the PackageDependency dependency in the application manifest when looking for dynamic extension libraries at startup can cause the WinUI 3 desktop application to mistakenly load WinUI 2's Microsoft.UI.Xaml.dll, causing the process to fail to start.
To solve this problem, we ensure that the application loads the correct version of Microsoft.UI.Xaml.dll by introducing dynamic dependencies and forcibly adjusting the loading order of the dependency packages to avoid startup failures due to version conflicts.
1. You must ensure that WinUI 2 and WinUI 3 dependency libraries appear in AppxManifest.xml, WinUI 2 dependency library name is Microsoft.UI.Xaml, The dependency library name for WinUI 3 is Microsoft.WindowsAppSDK.
2. The minimum system requirement for MSIX dynamic dependencies is Windows 11 22000(21H2)