Enable tests in images that don't have the VCLibs available

[guimafelipe]

With enabling the existing tests to run in the pipeline again, some of them needed to be added to the test's bypass list because some of the images don't have the VCLibs available.

Issue #5762 describes well the problem. Before, we were directly downloading the VCLibs from the link that is currently deprecated and are not sufficient to make the tests work.

The pull requests #5796, #5794, and #5719 all enables tests that needed to be added to the bypass list because of the lack of VCLibs available in the images. In special, in #5719 was disabled the manual installation of VCLibs from the deprecated source.

At this moment, the pipeline still downloads and deploys VCLibs from the deprecated source, so this can be reenabled if wanted by readding the task in the test pipeline yaml file, but my tests shown that it has no effect as the version is not the one required.

This should be fixed in the future with better way to manually and forcefully deploy VCLibs on images that does not have it.

Tests Disabled Due to Lack of VCLibs in Images

Test Suite	Images Affected
AccessControl Tests (Test::AccessControl::APITests::*)	release_x64_Windows.10.Enterprise.LTSC.2021 release_x64_Win10_rs5_DC release_x86_Windows.10.Enterprise.22h2 release_x86_Windows.11.Professional.23H2.zh-CN release_x86_Windows.Server.2019.DataCenter.zh-CN
AppLifecycle Tests (Test::AppLifecycle::FunctionalTests::*)	release_x64_Win10_rs5_DC release_x86_Windows.10.Enterprise.22h2 release_x86_Windows.11.Professional.23H2.zh-CN release_x86_Windows.Server.2019.DataCenter.zh-CN
OAuth2Manager Tests (OAuth2ManagerTests::OAuth2APITests::*)	release_x64_Windows.10.Enterprise.LTSC.2021 release_x64_Win10_rs5_DC release_x86_Windows.10.Enterprise.22h2 release_x86_Windows.11.Professional.23H2.zh-CN release_x86_Windows.Server.2019.DataCenter.zh-CN
PushNotificationTests	release_x64_Windows.10.Enterprise.LTSC.2021 release_x64_Win10_rs5_DC release_x86_Windows.10.Enterprise.22h2 release_x86_Windows.11.Professional.23H2.zh-CN release_x86_Windows.Server.2019.DataCenter.zh-CN

[DrusTheAxe]

Alternatively, those 4 tests could be updated to be build using the Hybrid CRT recipe. That should be picked up by default by all *.vcxproj in the repository. Unclear why these don't. Fix them?

[guimafelipe]

Alternatively, those 4 tests could be updated to be build using the Hybrid CRT recipe. That should be picked up by default by all *.vcxproj in the repository. Unclear why these don't. Fix them?

All of those tests uses test apps. These are apps that are packaged using a .wapproj packaging project.
The tests then try to install these packages, which is the moment the error happens for not having VCLibs available.

I don't know if being a .wapproj implicitly creates a dependency on VCLibs. What would be the correct alternative and direction for updating these test apps to use the Hybrid CRT?

[DrusTheAxe]

What would be the correct alternative and direction for updating these test apps to use the Hybrid CRT?

https://github.com/microsoft/WindowsAppSDK/blob/main/docs/Coding-Guidelines/HybridCRT.md

HybridCRT is just a recipe how you set certain properties to import the UCRT and statically link the rest (compiler helpers, std::vector<>, etc)

[DrusTheAxe]

I don't know if being a .wapproj implicitly creates a dependency on VCLibs

Good question. If .wapproj is forcefully injecting a <PackageDependency> on VCLibs then it's a problem. If it's doing this there should hopefully be a way to stop this.

@Scottj1s @alexlamtest ?