Exact version match does not find installation
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 991
- Forks
- 105
- PR merge metrics
- No merged PRs in 30d
Description
I'm finding I'm unable to use a simple inclusive range to find my visual studio installation using vswhere (Visual Studio Locator version 3.1.7+f39851e70f [query version 3.12.2140.44225]).
Expected behavior:
When Visual Studio 17.12.3 is installed and the -version argument is provided any of: [17], [17.12], [17.12.3], [17,17], [17.12,17.12] or [17.12.3,17.12.3] I would expect to find the installation.
Actual behavior:
The installation is not found.
Workaround:
An exact Visual Studio installation version can be found when using the inclusive and exclusive syntax together with a single increment to the exclusive value, like so: [17.12,17.13)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the -version queries listed in the issue against a Visual Studio 17.12.3 installation, then trace vswhere's version-range handling. Done means the inclusive exact-version forms find the installation, including [17.12.3,17.12.3], while the documented workaround continues to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli, devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100