-
Notifications
You must be signed in to change notification settings - Fork 510
Extension crash with Windows Powershell 5.1 : Exception encountered starting EditorServices #4483
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 @AlexBillon07 it looks like you are using our February release, can you confirm this reproduces with our latest release? |
You could try updating your .NET Framework...I have a hunch that's the problem and I'm not exactly sure what our supported minimum in the GAC scenario (Windows PowerShell 5.1) is right now. The code is checking for at least .NET Framework 4.6.2, but maybe that doesn't work any more. Link to downloads. If you really want to experiment, try 4.7, see if it repeats (maybe restart to be sure) and then repeat up until 4.8.1 🤷 |
Same issue with the last version.
@andschwa, I will try to update .NET Framework |
Hello, I have updated .NET Framework to version 4.8 and it works now. Thanks @andschwa |
Heck yeah! Thanks for the update. I will get the check we do in the codebase and the documentation updated. |
Prerequisites
Summary
Since I have upgraded from Windows 2012R2 to 2016, the Powershell extension crashes each time I try to create a session with Windows Powershell 5.1
I have installed Powershell 7.3.3 and it works fine. Unfortunately, for some reasons I have to be able to use VSCode with Windows Powershell 5.1.
PowerShell Version
Visual Studio Code Version
Extension Version
Steps to Reproduce
Launch a session with Windows Powershell (x64)
Visuals
Logs
StartEditorServices.log
vscode-powershell.log
The text was updated successfully, but these errors were encountered: