Please optimize the minimum version of the MSIX Dynamic Dependencies OS API to use

[Gaoyifei1011]

Please optimize the minimum version of the MSIX Dynamic Dependencies OS API to use

--------------------------

请优化一下 MSIX 动态依赖项 OS API 的最低使用版本

---

In the Windows App SDK MSIX Dynamic Dependency API of the main branch, if you use the system's dynamic dependency API, the minimum system version corresponds to 26100 (24H1), but the actual system's dynamic dependency API is 22000. Hopefully it will be optimized to the minimum version limit.

在 main 分支的 Windows App SDK MSIX 动态依赖项 API 中，如果使用系统的动态依赖项 API，最低系统版本对应 26100（24H1），但实际上系统的动态依赖项 API 是 22000。希望能优化到最低版本限制。

WASDK

WindowsAppSDK/dev/DynamicDependency/API/MsixDynamicDependency.cpp

Line 27 in 5902b27

if (MddCore::Win11::IsSupported())

WindowsAppSDK/dev/DynamicDependency/API/MddWin11.h

Line 45 in 5902b27

__declspec(selectany) bool g_isSupported{ WindowsVersion::IsWindows11_24H1OrGreater() };

Windows
https://learn.microsoft.com/zh-cn/windows/win32/api/appmodel/nf-appmodel-trycreatepackagedependency

[DrusTheAxe]

Please optimize the minimum version...

Do you have a specific need that brought this up?

In the Windows App SDK MSIX Dynamic Dependency API of the main branch, if you use the system's dynamic dependency API, the minimum system version corresponds to 26100 (24H1), but the actual system's dynamic dependency API is 22000.

This is ByDesign. WinAppSDK testing ran into a complication with the OS Dynamic Dependency API on 10.0.22000.0 that doesn't occur on 26100 (24H1). Rather than let perfect-be-the-enemy-of-the-good we enabled this optimization on 24H1 and continue relying on WinAppSDK's implementation for older systems.

There's a task in our backlog to unblock this down to 22000, though the effort/value/priority puts it behind other more significant and urgent work. I don't expect this to be addressed in the near term.

Win10 lacks OS Dynamic Dependency support + Win10 LTSC releases have years of support life yet == OS DynDep can't entirely obsolete WinAppSDK's DynDep implementation (at least, not anytime soon). As much as I'd love to see enhancements available across all systems and at the same time, that's not always feasible. The important goal is we (continue) to have functional parity across systems.

[Gaoyifei1011]

Please optimize the minimum version...

Do you have a specific need that brought this up?

In the Windows App SDK MSIX Dynamic Dependency API of the main branch, if you use the system's dynamic dependency API, the minimum system version corresponds to 26100 (24H1), but the actual system's dynamic dependency API is 22000.

This is ByDesign. WinAppSDK testing ran into a complication with the OS Dynamic Dependency API on 10.0.22000.0 that doesn't occur on 26100 (24H1). Rather than let perfect-be-the-enemy-of-the-good we enabled this optimization on 24H1 and continue relying on WinAppSDK's implementation for older systems.

There's a task in our backlog to unblock this down to 22000, though the effort/value/priority puts it behind other more significant and urgent work. I don't expect this to be addressed in the near term.

Win10 lacks OS Dynamic Dependency support + Win10 LTSC releases have years of support life yet == OS DynDep can't entirely obsolete WinAppSDK's DynDep implementation (at least, not anytime soon). As much as I'd love to see enhancements available across all systems and at the same time, that's not always feasible. The important goal is we (continue) to have functional parity across systems.

All right. However, I sincerely hope that future releases will optimize the system dynamic dependency API. Do you have the same problem testing on the 22621 series system?

[DrusTheAxe]

Do you have the same problem testing on the 22621 series system?

Unfortunately yes. 26100+ aka 24H2+ is good

Older systems are where the problems arose. This includes 22621 (aka 22H2 aka SV2) and 22631 (aka 23H2 aka SV3), and of course older.