Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Helix SDK] Support installing specific .NET SDKs **and** runtimes #6005

Closed
2 tasks
dougbu opened this issue Aug 20, 2020 · 3 comments · Fixed by #7158
Closed
2 tasks

[Helix SDK] Support installing specific .NET SDKs **and** runtimes #6005

dougbu opened this issue Aug 20, 2020 · 3 comments · Fixed by #7158
Assignees

Comments

@dougbu
Copy link
Member

dougbu commented Aug 20, 2020

  • This issue is blocking
  • This issue is causing unreasonable pain

Many repos specify .NET runtimes in their global.json files to ensure they're building against the latest before new SDKs are available. The Arcade SDK handles this pretty well (at least given .NET SDK restrictions around extending a globally-installed SDK ☹️).

But, the Helix SDK has no similar feature. For the dotnet/aspnetcore repo, this means we can only use the Helix SDK to install the .NET SDK. We then have to call dotnet-install ourselves and, on Linux, hack things together using symbolic links. We would not be testing against the latest dotnet/runtime bits otherwise.

The problem is the Helix SDK's .NET installation features are either / or: Either we ask the Helix SDK to install a .NET SDK or we request a .NET runtime. This issue is about adding an and option.

@garath
Copy link
Member

garath commented Aug 20, 2020

Triage: @dougbu How soon would you need this feature?

@dougbu
Copy link
Member Author

dougbu commented Aug 20, 2020

We have workarounds for the readonly SDK install location but it's a hack and @HaoK hasn't checked it in yet. See dotnet/aspnetcore#24287. This is about reducing the lifetime of that hack. So, sooner is better but not absolutely required.

@dougbu
Copy link
Member Author

dougbu commented Mar 23, 2021

This may be more urgent given concerns about flooding CDNs with requests from dotnet/aspnetcore's Helix work items. /cc @Pilchie

@HaoK HaoK self-assigned this Mar 25, 2021
@HaoK HaoK linked a pull request Mar 31, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants