Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / microsoft/vswhere issues and pull requests
#318 - Searching with `-find "**\bin\HostX64\x64\cl.exe"` takes 500s on Github Actions
Issue -
State: closed - Opened by touilleMan 2 months ago
- 2 comments
#317 - dll support
Issue -
State: closed - Opened by sapsari 3 months ago
- 2 comments
#316 - No output running in Docker
Issue -
State: closed - Opened by Linux13524 3 months ago
- 8 comments
#315 - Compilation fails
Issue -
State: open - Opened by mc0re 4 months ago
- 1 comment
#314 - What does it check for?
Issue -
State: closed - Opened by mc0re 4 months ago
- 5 comments
#313 - Remove Microsoft-related logos
Pull Request -
State: closed - Opened by LitoMore 5 months ago
- 3 comments
#312 - Python2 hangs calling vswhere since vs2022 update
Issue -
State: closed - Opened by ddevienne 6 months ago
- 1 comment
#311 - Update .vsts-compliance.yml to use managed identity
Pull Request -
State: closed - Opened by jlee671 7 months ago
#310 - One of my office PC fails to find MSVC when not running in elevated terminal.
Issue -
State: open - Opened by solarispika 8 months ago
- 6 comments
#309 - Update compliance pipeline to run all tools and log bugs
Pull Request -
State: closed - Opened by tydunkel 9 months ago
#308 - Convert CI pipeline to MicroBuild template
Pull Request -
State: closed - Opened by tydunkel 9 months ago
#307 - Updated a spelling mistake in user facing text.
Pull Request -
State: closed - Opened by 0xNinshu 11 months ago
- 6 comments
#306 - Provide a 64bits executable
Issue -
State: closed - Opened by malaterre 12 months ago
- 1 comment
Labels: wontfix
#305 - WARNING: Failed to activate VS environment: Could not parse vswhere.exe output
Issue -
State: closed - Opened by tarun253 12 months ago
- 1 comment
Labels: external
#304 - -version doesn't support pre-release suffixes
Issue -
State: closed - Opened by DamianEdwards about 1 year ago
- 3 comments
Labels: wontfix
#303 - Direct users to install wiki in README
Pull Request -
State: closed - Opened by heaths about 1 year ago
#302 - Add ability to locate Visual Studio Build Tools installations
Issue -
State: closed - Opened by lukaaash about 1 year ago
- 3 comments
#301 - vswhere could not detect VS2022
Issue -
State: closed - Opened by dharmateja27 about 1 year ago
- 8 comments
#300 - How do I find Visual Studio by year?
Issue -
State: closed - Opened by idbrii about 1 year ago
- 2 comments
#299 - too much code
Issue -
State: closed - Opened by act17 about 1 year ago
- 1 comment
#298 - Range Detection Issue
Issue -
State: closed - Opened by csteenwyk about 1 year ago
- 1 comment
#297 - -path is only for selection, not specifying a copied Visual Studio
Issue -
State: closed - Opened by MarkSchofield about 1 year ago
- 1 comment
Labels: wontfix
#296 - VS Buildtools 2022 17.7 not detected
Issue -
State: closed - Opened by Arthapz over 1 year ago
- 1 comment
#289 - Prepare vswhere and vswhere.lib to be Vulcan ready
Pull Request -
State: closed - Opened by skylarnam over 1 year ago
#288 - No detecting the installation of Remote Tools for Visual Studio
Issue -
State: closed - Opened by netkawai over 1 year ago
- 1 comment
Labels: external
#287 - Can we get an example in the wiki of selecting a specific version of VS?
Issue -
State: closed - Opened by Ershany over 1 year ago
- 3 comments
#286 - vswhere cannot find v17.5.0-pre.5.0 Build Tools on Arm64 device with -prerelease option
Issue -
State: closed - Opened by Blackhex almost 2 years ago
- 2 comments
Labels: duplicate, wontfix
#285 - Wiki documentation does not detect VSTest fom Build Tools
Issue -
State: closed - Opened by davisnw almost 2 years ago
- 1 comment
#284 - Provide weekly schedule for vswhere compliance run
Pull Request -
State: closed - Opened by Preecington almost 2 years ago
#283 - Provide weekly schedule for vswhere compliance run
Pull Request -
State: closed - Opened by Preecington almost 2 years ago
#282 - Removing dependency on non-compliant and outdated vswhere test package
Pull Request -
State: closed - Opened by Preecington almost 2 years ago
#281 - Update version.json to release from main
Pull Request -
State: closed - Opened by heaths about 2 years ago
#280 - Support DOS-like wildcards in -requires
Pull Request -
State: closed - Opened by heaths about 2 years ago
- 1 comment
#279 - Upgrade project, prepare GitHub flow
Pull Request -
State: closed - Opened by heaths about 2 years ago
- 1 comment
#278 - Publish winget package from publishing pipeline
Issue -
State: closed - Opened by heaths about 2 years ago
- 1 comment
#277 - Cannot locate msbuild on ARM64 installations
Issue -
State: closed - Opened by timheuer about 2 years ago
- 2 comments
#276 - `-requires` wildcard
Issue -
State: closed - Opened by ryanmkurtz about 2 years ago
- 9 comments
Labels: enhancement
#275 - Command doesn't return anything when only the buildtools are installed.
Issue -
State: closed - Opened by huntantr about 2 years ago
- 2 comments
#274 - Adding Microsoft SECURITY.MD
Pull Request -
State: closed - Opened by microsoft-github-policy-service[bot] about 2 years ago
#273 - `-path` flag does not appear in usage
Issue -
State: closed - Opened by lacasseio about 2 years ago
- 4 comments
#272 - How to find installations which support building SSDT projects?
Issue -
State: closed - Opened by chadbaldwin about 2 years ago
- 1 comment
#271 - -utf8 option seems not work
Issue -
State: closed - Opened by huhuang03 over 2 years ago
- 1 comment
#270 - -version does not allow for a single version value
Issue -
State: closed - Opened by tydunkel over 2 years ago
- 2 comments
#269 - Doesn't work for 'Visual Studio Build Tools xxxx'
Issue -
State: closed - Opened by zaufi over 2 years ago
- 1 comment
Labels: question, wontfix
#268 - Clarify -all documentation
Pull Request -
State: closed - Opened by heaths over 2 years ago
- 1 comment
#267 - Initialize console after parsing arguments (#263)
Pull Request -
State: closed - Opened by heaths over 2 years ago
#266 - -requires switch should accept path to .vsconfig file
Issue -
State: closed - Opened by AArnott over 2 years ago
- 2 comments
#265 - Clarify that `-all` switch excludes prereleases
Pull Request -
State: closed - Opened by AArnott over 2 years ago
- 14 comments
#264 - Add codepage integration tests
Issue -
State: open - Opened by heaths over 2 years ago
#263 - Initialize console after parsing arguments
Pull Request -
State: closed - Opened by heaths over 2 years ago
#262 - -utf8 option does not work
Issue -
State: closed - Opened by espresso3389 over 2 years ago
- 1 comment
#261 - vswhere does not find visual studio "MsBuildTool" edition
Issue -
State: closed - Opened by mucki-at over 2 years ago
- 2 comments
Labels: question
#260 - Upgrade agent to Server 2019 with VS2019
Pull Request -
State: closed - Opened by heaths over 2 years ago
- 4 comments
#259 - Release new version of vswhere
Pull Request -
State: closed - Opened by heaths over 2 years ago
#258 - vswhere could not detect VS2022 RTM version
Issue -
State: closed - Opened by 0x7FFFFFFFFFFFFFFF almost 3 years ago
- 5 comments
Labels: question
#257 - Unable to get only Visual Studio 2019 installation path
Issue -
State: closed - Opened by martin-braun almost 3 years ago
- 3 comments
Labels: question
#256 - extra bit set in state
Issue -
State: closed - Opened by kdschlosser almost 3 years ago
- 1 comment
Labels: question
#255 - This is more of a question then a problem I think.
Issue -
State: closed - Opened by kdschlosser almost 3 years ago
- 4 comments
Labels: question
#254 - Products wildcard does not find VS2022
Issue -
State: closed - Opened by mastercoms almost 3 years ago
- 2 comments
#253 - Find BuildTools installation paths
Issue -
State: closed - Opened by fgsfds almost 3 years ago
- 1 comment
Labels: duplicate
#252 - vswhere requires -prerelease to detect vs2022
Issue -
State: closed - Opened by gorlak almost 3 years ago
- 7 comments
#251 - Visual Studio 2022, Detect Microsoft.VisualStudio.Component.VC.Tools.x86.x64 for 142
Issue -
State: closed - Opened by TheOneRing about 3 years ago
- 3 comments
#250 - vswhere does not detect Visual Studio 2022 installations
Issue -
State: closed - Opened by japarson about 3 years ago
- 5 comments
#249 - vswhere could not detect VS2022 (preview)
Issue -
State: closed - Opened by shx0000123 about 3 years ago
- 4 comments
Labels: question, need-repro
#247 - vswhere stopped working with the -version switch
Issue -
State: closed - Opened by raymonvt about 3 years ago
- 2 comments
Labels: question, need-repro
#246 - Add compliance build and update minimum supported OS to Windows 7
Pull Request -
State: closed - Opened by tydunkel about 3 years ago
#245 - Update AzDO build to use new 1ES pool
Pull Request -
State: closed - Opened by tydunkel about 3 years ago
- 2 comments
#244 - Colorize vswhere output
Pull Request -
State: closed - Opened by heaths about 3 years ago
- 4 comments
#243 - Update microbuild pool to VS2019
Pull Request -
State: closed - Opened by davilimap over 3 years ago
#242 - Finding clang+llvm the right way
Issue -
State: closed - Opened by awakecoding over 3 years ago
- 5 comments
Labels: wontfix
#241 - vswhere doesn't find MSBuild on Windows 11 ARM64
Issue -
State: closed - Opened by dennisameling over 3 years ago
- 3 comments
#240 - Update docker image
Pull Request -
State: closed - Opened by lwillia over 3 years ago
#239 - Validate version range when min is 0
Pull Request -
State: closed - Opened by heaths over 3 years ago
- 2 comments
#238 - `-version` filter doesn't appear to work correctly when Dev17 installed
Issue -
State: closed - Opened by RussKie over 3 years ago
- 5 comments
#237 - Batch examples with -version <range>
Issue -
State: closed - Opened by KUGA2 over 3 years ago
- 8 comments
#236 - vswhere returns nothing when run from Cygwin SSH terminal
Issue -
State: closed - Opened by vinaydhegde over 3 years ago
- 13 comments
#235 - [Documentation] Better document the -products * switch
Issue -
State: closed - Opened by Chronial over 3 years ago
- 3 comments
#234 - Add X86 product ids
Pull Request -
State: closed - Opened by lwillia over 3 years ago
#233 - Does not find Visual Studio 2019 Community after feature update to Windows 10, version 20H2
Issue -
State: closed - Opened by swebb2066 over 3 years ago
- 8 comments
Labels: external
#232 - -requires does not find installed component
Issue -
State: closed - Opened by giuliov over 3 years ago
- 5 comments
#231 - Without "delims=" the batch file will not work
Pull Request -
State: closed - Opened by vonj over 3 years ago
- 1 comment
#230 - Add support for locating Visual Studio Build Tools without an installation of the IDE
Issue -
State: closed - Opened by resiina almost 4 years ago
- 2 comments
Labels: duplicate, wontfix
#229 - vswhere.exe doesn't find VS Build Tools 2019 ?
Issue -
State: closed - Opened by marcusl almost 4 years ago
- 1 comment
#228 - Typo in wiki page
Issue -
State: closed - Opened by k-takata almost 4 years ago
- 1 comment
Labels: bug
#227 - Get version of build tools
Issue -
State: closed - Opened by tommitytom about 4 years ago
- 1 comment
Labels: enhancement, wontfix
#226 - Check workloads and install what is missing
Issue -
State: closed - Opened by virginiarcruz about 4 years ago
- 5 comments
Labels: question
#225 - No product is found, although they are indeed installed
Issue -
State: closed - Opened by IngwiePhoenix over 4 years ago
- 10 comments
#224 - version number conventions
Issue -
State: closed - Opened by stefanseefeld over 4 years ago
- 1 comment
Labels: question
#223 - Advise wanted: vswhere output ends with sequence 0xD 0xA (CR LF)
Issue -
State: closed - Opened by BeErikk over 4 years ago
- 1 comment
Labels: enhancement, question, wontfix
#222 - Publish package for winget
Issue -
State: closed - Opened by heaths over 4 years ago
- 5 comments
Labels: enhancement
#221 - Typo in help text
Issue -
State: closed - Opened by uljo2 over 4 years ago
- 3 comments
#220 - vswhere doesn't work with multiple arguments to -requires
Issue -
State: closed - Opened by asklar over 4 years ago
- 6 comments
Labels: question, external
#219 - vwhere cannot locate buildtools in custom directories
Issue -
State: closed - Opened by vikpck over 4 years ago
- 1 comment
Labels: duplicate
#218 - Support for VS2019 preview
Issue -
State: closed - Opened by damon-kwok over 4 years ago
- 3 comments
Labels: question
#217 - vswhere does not find the vs 2017 C compiler installed by VS 2019 installer
Issue -
State: closed - Opened by PerMildner over 4 years ago
- 5 comments
Labels: external
#216 - vswhere.exe can't find VS2017 version 15.9.21 with -sort
Issue -
State: closed - Opened by LilyWangL over 4 years ago
- 1 comment
Labels: question
#215 - Find-VC needs update for Visual Studio 2019
Issue -
State: closed - Opened by PerMildner over 4 years ago
- 2 comments
Labels: need-repro
#214 - vswhere is not recognized as an internal or external command, operable program or batch file.
Issue -
State: closed - Opened by ganesh3 over 4 years ago
- 8 comments
Labels: question, need-repro
#213 - vswhere not finding VS2019 on new build agent
Issue -
State: closed - Opened by lesscodetxm over 4 years ago
- 6 comments
Labels: external
#212 - No output when running vswhere in a container in Kubernetes
Issue -
State: closed - Opened by keiransteele over 4 years ago
- 3 comments
Labels: external