Support PowerShell installed as .NET Core Global Tools

My issue related to following newsblog:

https://devblogs.microsoft.com/powershell/introducing-powershell-as-net-global-tool/

I have uninstalled PowerShell 6.2.2 to test installation via dotnet tool install --global PowerShell Everything is working fine.

Unfortunately, VSCode powershell extensions can’t automatically pick up PowerShell installed as .net core global tool and falls back to built-in windows powershell 5.1. For example, I can’t change language mode

Can you modify autodetection mechanics so powershell as global tools picked up correctly?

[JustinGrote]

Workaround

This is what I do for my scoop-installed powershells, you can do the same for the dotnet tools global folder

    "powershell.powerShellAdditionalExePaths": [
        {
            "exePath": "C:/Users/JGrote/scoop/apps/pwsh/current/pwsh.exe",
            "versionName": "Powershell"
        },
        {
            "exePath": "C:/Users/JGrote/scoop/apps/pwsh-preview/current/pwsh.exe",
            "versionName": "Powershell Preview"
        }
    ],

[SydneyhSmith]

@mromanch thanks for this comment, if you would like to have PowerShell show up as an option for Terminal:Default Shell please open an issue in VSCode’s repo as that is one of their editor commands that they would need to update to search for the global tool path…the additionalexespath setting influences the integrated console (rather than the terminal)…apologies for any confusion!