Skip to content
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

Windows PowerShell versions not enumerated correctly in 64-bit VS Code #1008

Closed
brwilkinson opened this issue Aug 24, 2017 · 3 comments
Closed
Labels
Issue-Bug A bug to squash.
Milestone

Comments

@brwilkinson
Copy link

brwilkinson commented Aug 24, 2017

code -v
1.15.1
41abd21afdf7424c89319ee7cb0445cc6f376959

vscode

$pseditor.EditorServicesVersion
Major Minor Build Revision


1 4 1 0

code --list-extensions --show-versions
bradygaster.azuretoolsforvscode@1.2.9
donjayamanne.python@0.7.0
eriklynd.json-tools@1.0.2
ipedrazas.kubernetes-snippets@0.1.3
johnpapa.azure-functions-tools@0.3.0
ms-vscode.csharp@1.12.1
ms-vscode.PowerShell@1.4.1
msazurermtools.azurerm-vscode-tools@0.3.6
PeterJausovec.vscode-docker@0.0.16
PKief.material-icon-theme@2.2.0

$psversiontable
Name Value


PSVersion 5.1.16273.1000
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.16273.1000
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

System Details

Windows 10 Insider

Issue Description

When I set the default powershell exe path to v 6 beta, I cannot swap back to ps 5.1

"powershell.powerShellExePath": "C:\Program Files\PowerShell\6.0.0-beta.5\powershell.exe",

If I comment out that property and just launch defaults, I can them swap between versions.

I used to be able to swap between when using v6Beta, however this stopped working.

vscode_powershell

@daviwil daviwil added this to the 1.4.2 milestone Aug 24, 2017
@daviwil
Copy link
Contributor

daviwil commented Aug 24, 2017

Thanks Ben!

daviwil added a commit to daviwil/vscode-powershell that referenced this issue Sep 5, 2017
This change introduces a new module that contains all the logic for
determining the current OS platform, process architecture and OS
architecture for use in determining available Windows PowerShell EXE
paths.  This module helps resolve problems that were introduced by the
new 64-bit distribution of Visual Studio Code.

Fixes PowerShell#1008
Fixes PowerShell#1007
Fixes PowerShell#1006
Fixes PowerShell#993
@daviwil daviwil changed the title Cannot find ps v5, when powershell.powerShellExePath set to 6.0.0-beta.5\\powershell.exe Windows PowerShell versions not enumerated correctly in 64-bit VS Code Sep 5, 2017
daviwil added a commit that referenced this issue Sep 5, 2017
This change introduces a new module that contains all the logic for
determining the current OS platform, process architecture and OS
architecture for use in determining available Windows PowerShell EXE
paths.  This module helps resolve problems that were introduced by the
new 64-bit distribution of Visual Studio Code.

Fixes #1008
Fixes #1007
Fixes #1006
Fixes #993
@daviwil daviwil closed this as completed in f2aa2a2 Sep 6, 2017
@brwilkinson
Copy link
Author

Thanks @daviwil looks good :)

@daviwil
Copy link
Contributor

daviwil commented Sep 6, 2017

Thanks for confirming!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug A bug to squash.
Projects
None yet
Development

No branches or pull requests

2 participants