Remove force install of Winget + Small improvements #2083
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Removes the forced install of winget on startup. Suppose a user clicks install on the applications page. In that case, winget will be installed anyways, but this removes the delay on bootup for users with a bad internet connection and only want to use winget for the tweaks or micro win. (Closes Not use winget but use chocolatey only #2076, Closes Remove winget and chocolately #2068, Closes Winget Auto Install #2039, Closes Winget Outdated...install takes FOREVER. #2022, Closes Don't be forced to install winget #2065) (Maybe it's possible to install winget in a separate Runspace but I haven't tested this)
Disables the unnecessary Progress bar on bootup which is normally shown when "Get-ComputerInfo" is run. The user doesn't care how long this takes, because the command runs in a separate Runspace anyway.
Adds a -Run Toggle in the Compile script so when developing and constantly recompiling and testing, it's easier to compile and run with a single command