Non-standard install of PowerShell does not load at session opening

[sangafabrice]

Prerequisites

• I have written a descriptive issue title.
• I have searched all issues to ensure it has not already been reported.
• I have read the troubleshooting guide.
• I am sure this issue is with the extension itself and does not reproduce in a standalone PowerShell instance.
• I have verified that I am using the latest version of Visual Studio Code and the PowerShell extension.
• If this is a security issue, I have read the security issue reporting guidance.

Summary

Hi,
When starting a new session of vscode-powershell, the default powershell execution path is used C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe although a non-standard install location was set.
Here is how the extension is set in settings.json:

{
  "powershell.powerShellAdditionalExePaths": [
      {
          "exePath": "X:\\Pwsh\\7\\pwsh.exe",
          "versionName": "PowerShell Core 7"
      }
  ],
  "powershell.powerShellDefaultVersion": "PowerShell Core 7",
}

Assuming that the non-standard location points to the PowerShell Core 7.2.3 executable, this is what is returned from the PowerShell Integrated Console instead:

PS > $PSVersionTable.PSVersion.Major
5

PowerShell Version

Name                           Value
----                           -----
PSVersion                      7.2.3
PSEdition                      Core
GitCommitId                    7.2.3
OS                             Microsoft Windows 10.0.19043
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}       
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Visual Studio Code Version

1.67.1
da15b6fd3ef856477bf6f4fb29ba1b7af717770d
x64

Extension Version

[email protected]

Steps to Reproduce

• Opens Visual Studio Code: code . --extensions-dir "X:\extensions"
• Start Powershell Integrated Console

Visuals

Logs

No response

[JustinGrote]

@sangafabrice thanks for opening an issue! FYI the giant yellow lines around your config should have been a clue, you're using the old syntax. Try it in the format below, it works fine for me!

[sangafabrice]

It works perfectly. Thank you. @JustinGrote

[andyleejordan]

Related to change made in #3919

[chawyehsu]

Related to change made in #3919

This is a BREAKING CHANGE and sadly there is no note elaborating this change. I believe a seamless migration stategy needs to be implemented, otherwise more newcomers could be missled by old documentation of this setting.

https://docs.microsoft.com/en-us/powershell/scripting/dev-cross-plat/vscode/using-vscode?view=powershell-7.2#adding-your-own-powershell-paths-to-the-session-menu=
https://stackoverflow.com/questions/61505287/
https://draith.azurewebsites.net/?p=400

[ghost]

Thank you for your comment, but please note that this issue has been closed for over a week. For better visibility, consider opening a new issue with a link to this instead.