`-c STS` is almost meaningless when the latest major release is an LTS (e.g. .NET 8)

Open
#418 14 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
powershell
Domain
cli

Research direction

Start by locating the install script's handling of the -c STS and -c LTS channel options, then review the issue discussion for an agreed selection rule. Done means the intended behavior for STS when LTS is newer is defined and the current 8.0.100 versus 7.0.404 example is addressed without requiring users to update channel IDs annually.

Written by the indexing model from the issue text.

Description

I believe that the -c STS option should consider both STS and LTS releases, rather than focusing exclusively on STS. Alternatively, there could be a different mode that selects the newer version between STS and LTS.

Currently, -c LTS (the default) installs SDK 8.0.100, while -c STS installs 7.0.404. It seems more practical to use -c 8.0 etc. and update the channel IDs once a year, if -c STS does not automatically choose the latest major release channel.

While the current approach might align with the distribution method of release files on Azure CDN, it's not particularly convenient for the script users.

Dominant language
PowerShell
Stars
213
Forks
120
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dotnet/install-scripts

All issues in dotnet/install-scripts

Similar issues

More CLI issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.