microsoft / microsoft/winget-pkgs
Microsoft.DotNet.SDK.*: Side-by-side installation of minor and patch releases
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 11.1k
- Forks
- 9.7k
- Avg merge
- 1h 32m
- Merged PRs (30d)
- 376
Description
.NET SDK minor and patch releases are installed side-by-side for the same major version. (I have checked this only for the .NET SDK 8 versions, but I assume it is like this for other major versions as well.) This is indeed necessary because there can be breaking changes within the same major version (intentional or due to bugs I don't know).
Despite the side-by-side installations, there are different package identifiers only for different major versions in WinGet, making it impossible to properly manage these installations using WinGet.
There should be a package identifier for each .NET SDK version instead or additionally.
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
Review the existing Microsoft.DotNet.SDK.* WinGet package identifiers and compare them with the side-by-side .NET SDK 8 installations described here. Determine the identifier scheme needed for each minor and patch release, then verify that it supports managing those installations independently.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100