Improve PowerShell 7 support #4949
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.
Pull Request (PR) description
This is attempt 2 in improving the PowerShell 7 support in Microsoft365DSC. The first attempt in #4916 was reverted with #4945.
This PR includes the optimization that
PSDesiredStateConfigurationin version 1.1 won't be uninstalled when runningUninstall-M365DSCOutdatedDependenciesand that the module handling withUpdate-M365DSCDependencies -ValidateOnlydoes not return false positives.@NikCharlebois Please advise on any errors you had, e.g. the issue with PowerShell ISE. I cannot reproduce that problem.
This Pull Request (PR) fixes the following issues