-
Notifications
You must be signed in to change notification settings - Fork 237
PSEditorServices doesn't work when machine is DeviceGuard enabled #754
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
We could just convert the whole start up script to a cmdlet. That would probably help with start up performance anyway. |
I have been thinking about exactly that as well |
As long as we can make it work properly across .NET platfroms, I'm onboard |
Side note so it doesn't get forgotten: Part of start up is creating a second runspace so we can use our custom host from |
I've always wondered why |
@SeeminglyScience did you mean a binary module? |
@tylerl0706 Yeah. The term "cmdlet" is sometimes used interchangeably with "command" but it does specifically refer to a command from a binary module. |
Any update on this? Is there a current workaround? Currently running into this issue with constrained language mode. |
No, we currently don't support Constrained Language Mode. We haven't prioritised the work, but may be able to get it as part of other work we're doing this year. |
I look forward to this getting fixed as well. VSCode not supporting constrained language mode has been a stumbling block for me for awhile now as well. |
I've also encountered this issue and I'm definitely looking forward to this getting fixed. |
@Jared-Harrington-Gibbs can you try the PowerShell Preview extension? That should have support for Constrained Language Mode. We can close this issue since this is in the PowerShell Preview extension. |
Uh oh!
There was an error while loading. Please reload this page.
Enterprises that leverage DeviceGuard has PowerShell running in constrained language mode which prevents VSCode+PS from working. Need to investigate what is happening and find appropriate solution.
The text was updated successfully, but these errors were encountered: