Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Pushing out updates to https://dot.net/v1/dotnet-install.sh
See original GitHub issueI made a change to the dotnet-install.sh script in master: https://github.com/dotnet/cli/commit/3fde06faf84161cf8b6d09a0be0ad16e059ec52d. What’s the best way to get this changed pushed to the release branches and https://dot.net/v1/dotnet-install.sh?
It’s a trivial change that doesn’t affect existing operating systems but adds support for additional ones that are known to be backwards compatible.
Without this change, other projects, such as as netcorecli-fsc (see https://github.com/dotnet/netcorecli-fsc/pull/90) regress on support for some operating systems. And with various changes coming down to the version of the script in the master branch, it seems like the version in master may not be safe to use for all cases.
Issue Analytics
- State:
- Created 7 years ago
- Comments:13 (11 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@tmds I implemented your suggestion as https://github.com/dotnet/cli/pull/6037
Done. @omajid so very sorry for the long time. Entirely my bad. I pushed it now, though I am not sure exactly how long it takes for it to light up.