For WinPS Adapter remove PS7 paths from PSModulePath #777
Conversation
This file contains hidden or 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
SteveL-MSFT
requested review from
mgreenegit,
theJasonHelmick and
michaeltlombardi
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.
PR Summary
The WinPS adapter is inheriting PS7 paths when
dscis run from PS7, this causes WinPS to find incompatible modules. The fix here is when WinPS adapter is used to explicitly remove PS7 paths from$env:PSModulePath.The other change is something I noticed and I think it was copied from the PS7 adapter but WinPS adapter doesn't need to worry about non-Windows so simplified the code.
PR Context
Fix #707