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 users lock down their version of .NET Core via global.json. They also have scripts that prepare for build which installs the corresponding .NET Core. However, the version has to be defined in two places or every script must get the version from global.json and pass it to the dotnet-install script.
I'd like to add a feature to dotnet-install.ps1 to allow users to pass in a path to a global.json which will be read and that exact version will be installed. I'm not sure how to parse JSON in bash but I can try to update dotnet-install.sh as well.
The text was updated successfully, but these errors were encountered:
I'm asking to have our scripts that call dotnet-install.ps1 to just pass the path to global.json rather than having to parse by itself. Not everyone is on Arcade so we have lots of repos with their own scripts that aren't updated or shared by some outside service.
As mentioned in the issue referenced for github/actions we have been looking to implement this feature in our setup-dotnet action. My preference would be to have the installer scripts just handle it so people just get this for free.
Many users lock down their version of .NET Core via
global.json
. They also have scripts that prepare for build which installs the corresponding .NET Core. However, the version has to be defined in two places or every script must get the version fromglobal.json
and pass it to thedotnet-install
script.I'd like to add a feature to
dotnet-install.ps1
to allow users to pass in a path to aglobal.json
which will be read and that exact version will be installed. I'm not sure how to parse JSON in bash but I can try to updatedotnet-install.sh
as well.The text was updated successfully, but these errors were encountered: