Closed kennykerr closed 4 months ago
@riverar lib.yml
uses vswhere
- I assume we can do the same in action.yml
to avoid these hardcoded paths?
We could, yup. I'm not really a fan of vswhere honestly but that's me.
I don't really care - just noticed that's what lib.yml does - I don't have it installed locally for some reason so I assume it doens't even come with Visual Studio.
It would just be nice not to have to hardcode these paths.
vswhere should always be installed with visual studio. And always in the same path: %ProgramFiles(x86)%\Microsoft Visual Studio\Installer\vswhere.exe
source: https://github.com/Microsoft/vswhere?tab=readme-ov-file#visual-studio-locator
Thanks!
In an attempt to fix #3054 build issues, I'm testing whether we can switch to the latest GitHub runners so that we can build with VS 2022 rather than 2019.
I expect action.yml will also need to be "fixed" as it has some hardcoded paths.