Why is the Windows App SDK's MSIX dynamic dependency API limited to non-packaged applications? #4819
Unanswered
Gaoyifei1011
asked this question in
General
Replies: 1 comment 1 reply
-
Can you provide some context on what your scenario for this is? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Why is the Windows App SDK's MSIX dynamic dependency API limited to non-packaged applications?
-------------------------------------------
为什么 Windows App SDK 的 MSIX 动态依赖项 API 仅限于非打包应用?
My project uses WinUI 2 and WinUI 3 together, WinUI 2 and WinUI 3 contain both Microshot.ui.xaml.dll dependency libraries, and I need to use the MSIX dynamic dependency API to resolve this conflict. When I use the Windows App SDK dynamic dependency API, I find that the Windows App SDK dynamic dependency API is limited to non-packaged applications, and packaged applications will directly fail to call this function. So I would like to ask if this API can be opened to packaging applications in the future?
-------------------------------------------
我的项目共同使用了 WinUI 2 和 WinUI 3,WinUI 2 和 WinUI 3 共同包含 Microsoft.UI.Xaml.dll 依赖库,需要使用 MSIX 动态依赖项 API 来解决这一冲突。当我使用 Windows App SDK 动态依赖项 API 时,发现 Windows App SDK 动态依赖项 API 仅限于非打包应用,打包应用调用该函数会直接失败。所以想问一下未来这个 API 可以开放给打包应用使用吗?
WindowsAppSDK/dev/DynamicDependency/API/MsixDynamicDependency.cpp
Line 36 in aa9c8b8
Beta Was this translation helpful? Give feedback.
All reactions