The Action fails with "Could not setup Developer Command Prompt"
See original GitHub issueAttempting to use the action like this:
name: Python package
on: [push]
jobs:
build:
runs-on: "windows-latest"
strategy:
matrix:
python-version:
- "2.7"
steps:
- uses: ilammy/msvc-dev-cmd@v1
results in a failure:
##[error]Could not setup Developer Command Prompt
##[error]Node run failed with exit code 1
Issue Analytics
- State:
- Created 4 years ago
- Comments:11 (5 by maintainers)
Top Results From Across the Web
Unable to install xcode command line developer tools
This prompts me to install the command line developer tools. When I click install I get the following error. Can't install the software...
Read more >How to use the Regsvr32 tool and ... - Microsoft Support
Describes how to use the Regsvr32 tool to register and unregister OLE controls. Also describes the error messages that may occur and what...
Read more >Debugging in Visual Studio Code
If running and debugging is not yet configured (no launch.json has been ... port is announced in the Debug Console, and typically, the...
Read more >Troubleshoot WorkSpace authentication issues when using ...
"Directory Unavailable: Your directory could not be reached at this time. ... with the WorkSpace in the WorkSpaces console or welcome email.
Read more >DevicePolicyManager - Android Developers
Any application calling an api may only pass as an argument a device ... General failure to set the Private DNS mode, not...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Maybe I misunderstood what this action is for. Looking at the debug output and some of the code, it looks like it is not for installing Visual Studio. Instead, it is for activating one of the existing installations that is already included in the GitHub Windows environment. Is that right?
More info:
For the MSVC toolset, Visual Studio 2019 supports up to v142, while Visual Studio 2017 only supports up to v141. If you want to use MSVC v142 with VS 2017, you will encounter some errors like this: c++ - How to install (v142) Build tools in Visual studio - Stack Overflow
For the GitHub Actions runners, we can learn which components have been installed by reading the documentation. Search “Microsoft.VisualStudio.Component.VC” in Windows2016-Readme.md and Windows2019-Readme.md , and you will get what you need.
I don’t know if it is possible to install a too old toolset on the runner (e.g., 9.0), but I believe that Microsoft discourages developers from doing this.