Hacker News new | ask | show | jobs
by Kuinox 789 days ago
I do not understand the usecase for dotnet, since the dotnet SDK self select the correct version to run the project. You never need to change the version yourself. On my current machine:

    PS C:\Users\username> dotnet --list-sdks
    7.0.408 [C:\Program Files\dotnet\sdk]
    8.0.101 [C:\Program Files\dotnet\sdk]
    8.0.104 [C:\Program Files\dotnet\sdk]
    8.0.204 [C:\Program Files\dotnet\sdk]
    8.0.300-preview.24118.4 [C:\Program Files\dotnet\sdk]
IMO it's a better way to handle this sort of problem: the SDK self select which version should run, according to your project config.
1 comments
AaronFriel 789 days ago
For runtimes with tooling like .NET has, it's a niche use case.

At $dayjob, we have to support non-current compilers/SDKs for five different languages and runtimes where our tool will invoke (shell out, often) the CLIs for those tools. When triaging a bug report, it's great to have a version manager to use exactly the customer's version of the CLI.

Likewise, we need to make sure all of our examples and templates build even if the user has an old version, and the surest way to validate that is to hide newer CLIs and tools, and to test on the range of binaries that a customer could have installed.

link