You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched all issues to ensure it has not already been reported.
Summary
If the PowerShell setting for assigning additional execution paths (powershell.powerShellAdditionalExePaths) is used with an invalid versionName parameter shown within the snippet down below no warning appears.
This can lead to an unnoticed use of a different PowerShell version than defined seemingly within the settings since the value "Windows PowerShell 5.1 (x86)" for the parameter VersionName is not valid.
Instead, the correct value should be "Windows PowerShell (x86)".
Prerequisites
Summary
If the PowerShell setting for assigning additional execution paths (powershell.powerShellAdditionalExePaths) is used with an invalid versionName parameter shown within the snippet down below no warning appears.
This can lead to an unnoticed use of a different PowerShell version than defined seemingly within the settings since the value "Windows PowerShell 5.1 (x86)" for the parameter VersionName is not valid.
Instead, the correct value should be "Windows PowerShell (x86)".
Proposed Design
This manner could be accomplished by either informing the user or accepting the user-defined value for parameter versionName.
The text was updated successfully, but these errors were encountered: