Aniruddha Kanhere 8102d351eb CI: locate Visual Studio via vswhere instead of hardcoded Enterprise path (#1413) ...

The 'Install Glib' step in the Windows Simulator demo jobs (corePKCS11,
core libraries, FreeRTOS+TCP) hardcoded the VS 2022 *Enterprise* path to
Launch-VsDevShell.ps1. The GitHub windows-latest runner image no longer
provides Visual Studio under that edition path, so the step fails with
'Launch-VsDevShell.ps1 ... is not recognized' and all three WinSim demo
jobs error out.

Use vswhere.exe (which lives at a fixed, edition-independent location) to
discover the VS installation path at runtime, then invoke the located
Launch-VsDevShell.ps1.

2026-06-19 14:29:16 -07:00

..

auto-release.yml

Update auto-release.yml

2025-07-09 13:15:21 -07:00

ci.yml

FreeRTOS_Plus_TCP_Echo_Qemu_mps2: cleanup (#1336)

2025-04-21 19:13:02 +05:30

core-checks.yml

FreeRTOS_Plus_TCP_Echo_Qemu_mps2: cleanup (#1336)

2025-04-21 19:13:02 +05:30

freertos_demos.yml

Update download locations to outside repository content (#1355)

2025-06-05 23:21:31 +05:30

freertos_mpu_demo.yml

Update Cortex R4F and Cortex R5F MPU Demos (#1200)

2024-03-28 12:37:03 -07:00

freertos_plus_demos.yml

CI: locate Visual Studio via vswhere instead of hardcoded Enterprise path (#1413)

2026-06-19 14:29:16 -07:00

kernel-unit-tests.yml

FreeRTOS_Plus_TCP_Echo_Qemu_mps2: cleanup (#1336)

2025-04-21 19:13:02 +05:30