You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Probably there should be a command-line parameter that controls this (ie --include-previews).
Additionally, checking _sdkVersion.Prerelease may not be the best option for the default behavior. A better option may be to base it on whether the SDK Feature band is a prerelease band. That way the behavior of stabilized and non-stabilized RTM-branded SDKs would be the same, where today it isn't.
Finally, currently if you run dotnet workload search version --include-previews, you get an IndexOutOfRangeException, instead of an error that --include-previews is unrecognized.
The text was updated successfully, but these errors were encountered:
I can add support for --include-previews. (I think we'd originally discussed it as 'if people ask, we can add it' rather than building it in by default, but I think it's a pretty reasonable ask.) Why is having a non-stabilized RTM-branded SDK acting like a stable SDK a good thing?
Edit: I actually started working on this, started testing, and changed my mind.
Currently, when searching for workload sets, the SDK will include preview versions if the .NET SDK itself is branded as preview:
sdk/src/Cli/dotnet/commands/dotnet-workload/search/WorkloadSearchVersionsCommand.cs
Line 79 in 54abeef
Probably there should be a command-line parameter that controls this (ie
--include-previews
).Additionally, checking
_sdkVersion.Prerelease
may not be the best option for the default behavior. A better option may be to base it on whether the SDK Feature band is a prerelease band. That way the behavior of stabilized and non-stabilized RTM-branded SDKs would be the same, where today it isn't.Finally, currently if you run
dotnet workload search version --include-previews
, you get anIndexOutOfRangeException
, instead of an error that--include-previews
is unrecognized.The text was updated successfully, but these errors were encountered: