Does not work with toolset 14.28 on `windows-latest`

And in general, why not using the latest version of msvc in the README.md then show how to use older versions.

workflow file

    runs-on: windows-latest

    steps:
      - uses: ilammy/msvc-dev-cmd@v1
        with:
          arch: amd64
          toolset: 14.28

output

Run ilammy/msvc-dev-cmd@v1
Found with vswhere: C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Auxiliary\Build\vcvarsall.bat
Error: Could not setup Developer Command Prompt: invalid parameters
[ERROR:vcvars.bat] Toolset directory for version '14.28' was not found.
[ERROR:VsDevCmd.bat] *** VsDevCmd.bat encountered errors. Environment may be incomplete and/or incorrect. ***
[ERROR:VsDevCmd.bat] In an uninitialized command prompt, please 'set VSCMD_DEBUG=[value]' and then re-run
[ERROR:VsDevCmd.bat] vsdevcmd.bat [args] for additional details.
[ERROR:VsDevCmd.bat] Where [value] is:
[ERROR:VsDevCmd.bat]    1 : basic debug logging
[ERROR:VsDevCmd.bat]    2 : detailed debug logging
[ERROR:VsDevCmd.bat]    3 : trace level logging. Redirection of output to a file when using this level is recommended.
[ERROR:VsDevCmd.bat] Example: set VSCMD_DEBUG=3
[ERROR:VsDevCmd.bat]          vsdevcmd.bat > vsdevcmd.trace.txt 2>&1

[ilammy]

That said, I tried to reproduce the error on a new repo with a quasi-identical workflow, and it is working fine.

This might be caused by some action runner shenanigans. windows-latest might mean slightly different environments, they upgraded on per-repo basis. But it seems that 14.28 should be included in all versions that they ship. See actions/virtual-enviroments.

One thing to note is that neither this action, nor egor-tensin/vs-shell are installing MSVC components. They merely set up the environment for tools that are already installed in the system. If the tools are no there then they’re not there. For example, if you’re using private action runners, then that’s the administrator’s responsibility to install all the components.

Comparing the environments might shed some light onto this. The first step “Set up job” will output details:

Current runner version: '2.278.0'
Operating System
  Microsoft Windows Server 2019
  10.0.17763
  Datacenter
Virtual Environment
  Environment: windows-2019
  Version: 20210516.0
  Included Software: https://github.com/actions/virtual-environments/blob/win19/20210516.0/images/win/Windows2019-Readme.md
  Image Release: https://github.com/actions/virtual-environments/releases/tag/win19%2F20210516.0

If both workflows use exactly the save environment version but one fails while other does not – that’s weird. However, if a failing one has a different environment, that might be the reason.

[pzhlkj6612]

Oh, thank you guys for sharing. I didn’t know this before.