-
Notifications
You must be signed in to change notification settings - Fork 498
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
Loading temporary ExtensionService script causes error loop when execution policy locked to AllSigned #784
Comments
Weird... Not sure why the error keeps getting written repeatedly, looks like it's getting stuck in a loop. Will investigate! |
daviwil
changed the title
Enforced execution policy still causing problems
Loading temporary ExtensionService script causes error loop when execution policy locked to AllSigned
May 25, 2017
daviwil
added a commit
to daviwil/PowerShellEditorServices
that referenced
this issue
Jun 3, 2017
This change adds a new PowerShellEditorServices.Commands module that gets loaded inside of the editor session's runspace to provide functions and cmdlets which are useful when working with the $psEditor APIs. This will also be the place where built-in "editor commands" are registered when the session initializes. Resolves PowerShell#403. Resolves PowerShell/vscode-powershell#784.
daviwil
added a commit
to daviwil/PowerShellEditorServices
that referenced
this issue
Jun 3, 2017
This change adds a new PowerShellEditorServices.Commands module that gets loaded inside of the editor session's runspace to provide functions and cmdlets which are useful when working with the $psEditor APIs. This will also be the place where built-in "editor commands" are registered when the session initializes. Resolves PowerShell#403. Resolves PowerShell/vscode-powershell#784.
daviwil
added a commit
to PowerShell/PowerShellEditorServices
that referenced
this issue
Jun 3, 2017
This change adds a new PowerShellEditorServices.Commands module that gets loaded inside of the editor session's runspace to provide functions and cmdlets which are useful when working with the $psEditor APIs. This will also be the place where built-in "editor commands" are registered when the session initializes. Resolves #403. Resolves PowerShell/vscode-powershell#784.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
System Details
$PSVersionTable
:Name Value
PSVersion 5.1.14393.1066
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.14393.1066
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
Issue Description
Domain enforced execution policy of AllSigned still causing problems. The PowerShell Editor Services module, specifically the ExtensionService, is writing PS script to files in the temp folder prior to execution, rather than executing it directly, to avoid creating a lot of noise in the logs (according to source comments). However, the execution of the files fails because they are not signed.
Attached Logs
1495713868-7e829c45-df99-45e5-8a0b-b66def66d6361495713858270.zip
Follow the instructions in the README
about capturing and sending logs.
The text was updated successfully, but these errors were encountered: