-
Notifications
You must be signed in to change notification settings - Fork 512
Support PowerShell installed as .NET Core Global Tools #2110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Thanks for opening this issue @maximpashuk it looks like we need to incorporate ~.dotnet\tools\pwsh.exe into the paths we check for all available PowerShell versions on a system. |
WorkaroundThis is what I do for my scoop-installed powershells, you can do the same for the dotnet tools global folder
|
According to |
This does not work for me. I just tried re-installing
Expected behavior: The list of available shells will include Actual behavior: There is no The VS Code version: Code 1.46.1 (cd9ea6488829f560dc949a8b2fb789f3cdc05f5d, 2020-06-17T21:13:20.174Z)
System Info
Extensions (33)
(10 theme extensions excluded) |
@mromanch thanks for this comment, if you would like to have PowerShell show up as an option for |
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?
The text was updated successfully, but these errors were encountered: