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
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: