Boxstarter doesn't override 'Write-Host' when in any non-Boxstarter shell/script #561
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.
Description Of Changes
Ensure Boxstarter is added to the end of PSModulePath when being installed, this way 'Write-Host' is not loaded from Boxstarter but 'Microsoft.PowerShell.Utility' (or whatever comes first)
Motivation and Context
See GH-528 - Boxstarter gets installed to top of PSModulePath and overwrites Write-Host
Testing
I've tested this via creating the Chocolatey-nupkgs using the buildscript, - it works as expected when installing/upgrading via Chocolatey as well as when using the Boxstarter.bat wrapper.
Operating Systems Testing
Change Types Made
Change Checklist
Related Issue
Fixes #528