Temporary workaround for broken `vswhere.exe`
See original GitHub issueThere is a regression in the internal preview of VS where the vswhere
tool does not report correct version of VS.
To unblock dogfooders this, we’ve put a workaround in place: https://github.com/dotnet/arcade/pull/12721
We should revert this workaround once this gets fixed by VS.
This issue is a reminder to remove the workaround.
Issue Analytics
- State:
- Created 7 months ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
vswhere not reporting any installs after 2019 #178
After a complete uninstall of both products and reinstall of ONLY 2017, vswhere refuses to find my install, which is breaking my builds....
Read more >Troubleshoot Visual Studio installation and upgrade issues
To see if there's a workaround for your problem, check Known Issues of ... Then, run the executable to reset your installation metadata....
Read more >First I had problems with edit and continue, after repair this ...
A fix would be nice] After repair option of the installer. I don't know if this is relevant but Visual studio 2022 is...
Read more >Programmatically finding the VS2017 installation directory
You can use vswhere tool to get VS2017 location. Example: @echo off rem VS2017U2 contains vswhere.exe if "%VSWHERE%"=="" set ...
Read more >Invoke-MsBuild.psm1 2.6.1
Executes the MsBuild.exe tool against the specified Visual Studio solution or project file. Returns a hash table with properties for determining if the ......
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
Just floating the context from an email thread here for book-keeping - the VS team has found a second bug and should have this fixed before the official rollout of preview 2
I understand a fix happened on VS’ side in the end and so there’s no workaround after all. I believe we can close this, @wtgodbe can correct me