Integrated Console doesn't start when missing powerShellExePath setting #1006
Comments
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
|
Wasn't actually able to reproduce this issue when I tried it, but I made sure that the correct default value will get sent through no matter what. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The latest VS Code Insiders builds have caused a change in behavior which causes the PS Integrated Console to not launch when the
"powershell.powerShellExePathsetting isn't specified. There must have been an API change related to default setting values.The text was updated successfully, but these errors were encountered: