-
Notifications
You must be signed in to change notification settings - Fork 510
PowerShellEditorServices.Commands.psd1
MissingMethodException
#3297
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
One unusual thing is that this is x86 Windows PowerShell running on a 64-bit Windows. @anankee26 can you report the output of this: |
Hi @rjmholt
|
@anankee26 do you get this error when running from 64-bit Windows PowerShell? (the one that isn't called |
@rjmholt, no error with the powershell core 7.1.3 x64 installed next to the two windows powershell 5.1. This config was working a few weeks ago; the last time I used vscode to do powershell (not the exact date). When I tried to do it again at the beginning of this week: it didn't work anymore. |
Hi,
EditorServices.log:
|
So it looks like there's an issue between the version of the assembly you're loading on your machine vs the one Editor Services expects (indirectly through a dependency). Essentially it seems something deep down expects What's strange about this is that the logs indicate that the relevant DLL was loaded from the extension's path on your machine:
So basically you're loading the version of the DLL we ship, but it's breaking with the rest of the program and only for you. So I still don't really understand what's going on here. |
hello, I tried a complete uninstall of VScode (with profil deleted) and re-install in
with only the powershell add-on in 2021.5.1 but nothing to do, still impossible to start windows powershell 5 now, with the new version of VsCode, I have this message that appears in the terminal at startup:
and in editorservices.log
and in vscode-powershell.log
I don't know where to look for a solution anymore... |
I think this may be related to issues in general with the assemblies shipped for PowerShell 5.1 support. Our use of .NET 6 (because of our support of PowerShell 7.2.x) brought in a bug with |
Hey @anankee26 can you try this insider build of the extension and see if it fixes your issue? |
Hello @andschwa vscode update in
EditorServices.log:
StartEditorServices.log = empty vscode-powershell.log:
|
Hi, |
Hm, that |
But your error with v2021.5.1 is very different from your original error with v2021.2.2. I guess we should debug the former since the latter has gone away? |
Hello @andschwa yes the first error with v2021.2.2 doesnt't appear now. I agree that it is better to debug the one that is currently present with v2021.2.2. |
PowerShellEditorServices.Commands.psd1
MissingMethodException
@anankee26 I've lost track of what the bug is here. I'm going to mark this resolved because your original issue in v2021.2.2 as we discovered was resolved by updating to v2021.5.1. Could you please open a new bug for your new issue? Thanks! |
OK, done in #3462 |
Thanks!! |
Hello,
The powershell terminal in v5.1 doesn't start anymore: it stays stuck in "starting powershell". This does not happen with the PS terminal in 7.1.3.
In the editorServices.log, I have this message:
Tried to downgrade to old vscode and addon version: same error.
Logs vscode in diagnostic mode attached.
Thx for support.
powershell editor services.txt
StartEditorServices.log
vscode-powershell.log
EditorServices.log
Steps to reproduce
Expected behavior
Actual behavior
Environment data
VScode version:
Addon Powershell version: 2021.2.2
The text was updated successfully, but these errors were encountered: