microsoft/vswhere issues and pull requests

#211 - vswhere hangs (2020 edition)

Issue - State: closed - Opened by timmkrause over 4 years ago - 11 comments
Labels: need-repro, external

#210 - -version argument causes 'Error 0x57: Argument expected' - when called from batch file

Issue - State: closed - Opened by TFSUser1 over 4 years ago - 6 comments
Labels: external

#209 - vswhere from within Activated Environment

Issue - State: closed - Opened by davidbrownell almost 5 years ago - 1 comment
Labels: wontfix

#208 - Current choice of characters for the version range is unfortunate (cmd.exe)

Issue - State: closed - Opened by assarbad almost 5 years ago - 5 comments
Labels: blocked

#207 - Specify multiple properties?

Issue - State: closed - Opened by cniggeler almost 5 years ago - 2 comments
Labels: question, wontfix

#206 - -version 15.0 return 15 and 16

Issue - State: closed - Opened by sinukus almost 5 years ago - 1 comment
Labels: question

#205 - Powershell will help full

Issue - State: closed - Opened by dhmuralikrishna almost 5 years ago - 4 comments
Labels: wontfix

#204 - Fixes Visual Studio 2010 C++ compiler detection.

Pull Request - State: closed - Opened by lygstate almost 5 years ago - 1 comment

#203 - vswhere didn't detected VS 2010 when only Windows 7.1 SDK are installe.

Issue - State: closed - Opened by lygstate almost 5 years ago - 3 comments
Labels: need-repro

#202 - vswhere isn't finding Visual Studio 2019

Issue - State: closed - Opened by dewilcox about 5 years ago - 2 comments
Labels: question

#201 - Optionally output packages

Pull Request - State: closed - Opened by heaths about 5 years ago

#200 - vshere - what if enterprise and professional version of Visual Studio is installed on machine

Issue - State: closed - Opened by rguabhi9 about 5 years ago - 4 comments
Labels: question

#198 - Unable to find suitable Visual Code toolchain. Visual Studio 2019 Community problem.

Issue - State: closed - Opened by Ali-NS about 5 years ago - 6 comments
Labels: question, external

#196 - Why not provided as global tool?

Issue - State: closed - Opened by TFTomSun about 5 years ago - 12 comments
Labels: enhancement, wontfix

#185 - Document the -version command-line argument

Issue - State: closed - Opened by IanKemp over 5 years ago - 5 comments
Labels: question

#181 - Any plans on creating an npm package

Issue - State: closed - Opened by canpolat over 5 years ago - 7 comments

#161 - Find MSBuild 16 (VS2019) with vswhere

Issue - State: closed - Opened by zivkan over 5 years ago - 11 comments

#136 - Find `tf.exe` example

Issue - State: closed - Opened by jessehouwing over 6 years ago - 6 comments
Labels: invalid

#130 - vswhere could not detect Build Tools or Express editions

Issue - State: closed - Opened by dgiebel over 6 years ago - 2 comments
Labels: invalid, wontfix

#126 - VSTest instructions do not work for VS Test Agent 2017

Issue - State: closed - Opened by jnm2 over 6 years ago - 15 comments
Labels: enhancement, question

#122 - Please add vswhere to scoop

Issue - State: closed - Opened by dariusdamalakas almost 7 years ago - 4 comments
Labels: enhancement

#41 - Searching of MSBuild tools: vswhere + VS as an initial tool by default

Issue - State: closed - Opened by 3F over 7 years ago - 36 comments
Labels: enhancement

#8 - Support the BuiltTools SKU

Pull Request - State: closed - Opened by refack over 7 years ago - 7 comments
Labels: cla-not-required

Ecosyste.ms: Issues

GitHub / microsoft/vswhere issues and pull requests