vswhere: Cannot distinguish releases from prereleases
Some internal and external users have asked for a way to filter out prereleases. Visual Studio ships a number of prereleases to our preview channel before releasing the final updated versions. Currently, this information is not exposed through the query API but we are working to make it so.
This is a tracking item and a request for comments on how to expose this ability.
Currently, I have a prototype which,
- Filters out prereleases by default.
- Adds a
IsPrerelease : booleanproperty. - Adds a
-prereleaseswitch parameter to vswhere.exe to allow prereleases in results.
This means prereleases will no longer show up in results by default, but you can opt into considering prereleases with the -prerelease switch.
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 21 (10 by maintainers)
Commits related to this issue
- Support detection of prereleases Resolves issue #79 — committed to microsoft/vswhere by heaths 7 years ago
- Support detection of prereleases Resolves issue #79 — committed to microsoft/vswhere by heaths 7 years ago
But vswhere is bundled with Visual Studio right? So updating Visual Studio updates your vswhere.
Anyway, if it’s not going to make a difference then 🤷♂️ , although I guess it might be worth bumping so that if people see that vswhere got updated from
1.0.xto2.0.xthen that might give them a clue that reading the release notes would be a good idea.I considered
-noprereleasebut others expressed interested in this behavior by default. If preview deployments were more prevalent, I would be inclined to agree to opt out of seeing them. In most implementations such as NuGet and NPM, you opt into seeing prereleases so figured normalcy over vswhere back-compat for a relatively young project (i.e. break behavior now while it’s young).Thanks for all your comments.