Switching between PowerShell versions on Windows is unreliable #737
Comments
|
For me the integrated console hangs when I run the "PowerShell: Restart Current Session" command. Not sure if that is related, or if it should be logged as an issue of its own. |
|
I think it's the same issue, I'll look into it today. |
daviwil
added a commit
to daviwil/vscode-powershell
that referenced
this issue
May 26, 2017
This change fixes some issues with switching and restarting the active PowerShell session after our migration to the new vscode-languageclient package. They changed their error handling code in a way that caused our shutdown process to get stuck in a loop. Fixes PowerShell#737 Fixes PowerShell#782
daviwil
added a commit
to daviwil/vscode-powershell
that referenced
this issue
May 30, 2017
This change fixes some issues with switching and restarting the active PowerShell session after our migration to the new vscode-languageclient package. They changed their error handling code in a way that caused our shutdown process to get stuck in a loop. Fixes PowerShell#737 Fixes PowerShell#782
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It appears that after the latest upgrade to
vscode-languageserverwe've lost the ability to switch between PowerShell versions cleanly using the status bar menu. Sometimes it hangs at startup causing the extension host to crash after a timeout. Other times it seems to work fine. There must be some initialization step that we need to clean up when using the newer version of that library./cc @jpsnover
The text was updated successfully, but these errors were encountered: