Fix PSVersion check in Get-FormatData to return format data
#8063
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 FormatData format changed in version 5.1 so during remoting a client specifies the version of PowerShell FormatData it can understand.
In the case of FileInfo (and DirectoryInfo), the format requires 5.1 so remoting must pass the
-PowerShellVersion 5.1parameter to successfully get format data. There is a bug in the logic to validate the version and it was validating the build number. So the version string5.1fails this check because it does not include a version number (which defaults to -1). The fix is to remove the check on the build number and simply rely on major version and minor version.Fix #4237
PR Checklist
.h,.cpp,.cs,.ps1and.psm1files have the correct copyright headerWIP:to the beginning of the title and remove the prefix when the PR is ready.[feature]if the change is significant or affects feature tests