.NET Global Tool versus MSI install for vscode

[vale-tech]

Installing this as a .NET global tool is easy, but the default install location is %UserProfile%.dotnet\tools but this is not available to the Select default shell function when using VSCode on Windows. Using the MSI and getting an install in C:\Program Files works much better with respect to VSCode. I also tried installing as a .NET tool using the --tool-path option to install to the MSI directory, but the pwsh.exe was still not available to the Select default shell function.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 46356aae-d82e-63ce-63cf-fe10cd47d76d
• Version Independent ID: c5ccf493-dc82-bb65-830a-d5857048ce26
• Content: Installing PowerShell Core on Windows - PowerShell
• Content Source: reference/docs-conceptual/install/Installing-PowerShell-Core-on-Windows.md
• Product: powershell
• Technology: powershell-conceptual
• GitHub Login: @joeyaiello
• Microsoft Alias: jaiello

[sdwheeler]

@TylerLeonhardt @rjmholt Isn't this is fixed in an upcoming build of the PowerShell extension?

[rjmholt]

Not yet. @adityapatwardhan what versions of the dotnet global tool are affected by the startup bug?

[rjmholt]

Isn't this is fixed in an upcoming build of the PowerShell extension?

The answer is now yes, the next one

[sdwheeler]

Closing this issue since the problem is fixed in the next release.