c# - 使用 C# 中的调用命令引发异常

Question

我从 powershell 终端尝试了以下案例：

invoke-command -connectionuri "http://FullMachineName/wsman" -configuration "http
://schemas.microsoft.com/powershell/Microsoft.PowerShell" -credential "MachineName\Administrator" -filepath "C:\scripts\get
Users.ps1"

这工作正常。但是，当我通过 C# 的调用命令尝试相同的事情时，它会引发以下异常：

System.Management.Automation.CmdletInvocationException was unhandled
  Message=File C:\scripts\getUsers.ps1 cannot be loaded because the execution of scripts is disabled on this system. Please see "get-help about_signing" for more details.
  Source=System.Management.Automation
  WasThrownFromThrowStatement=false
  StackTrace:
       at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
       at System.Management.Automation.Runspaces.LocalPipeline.InvokeHelper()
       at System.Management.Automation.Runspaces.LocalPipeline.InvokeThreadProc()
  InnerException: System.Management.Automation.PSSecurityException
       Message=File C:\scripts\getUsers.ps1 cannot be loaded because the execution of scripts is disabled on this system. Please see "get-help about_signing" for more details.
       Source=System.Management.Automation
       WasThrownFromThrowStatement=false
       StackTrace:
            at System.Management.Automation.AuthorizationManager.ShouldRunInternal(CommandInfo commandInfo, CommandOrigin origin, PSHost host)
            at Microsoft.PowerShell.Commands.PSExecutionCmdlet.GetScriptBlockFromFile(String filePath)
            at Microsoft.PowerShell.Commands.PSExecutionCmdlet.BeginProcessing()
            at Microsoft.PowerShell.Commands.InvokeCommandCommand.BeginProcessing()
            at System.Management.Automation.Cmdlet.DoBeginProcessing()
            at System.Management.Automation.CommandProcessorBase.DoBegin()
       InnerException: System.UnauthorizedAccessException
            Message=File C:\scripts\getUsers.ps1 cannot be loaded because the execution of scripts is disabled on this system. Please see "get-help about_signing" for more details.
            InnerException: 

我正在尝试使用以下代码：

String file = @"C:\scripts\getUsers.ps1";
PowerShell ps = PowerShell.Create()
PSCommand cmd = new PSCommand();                
cmd.AddCommand("Invoke-Command");
cmd.AddParameter("CONNECTIONURI", "http://FullMachineName/wsman");
cmd.AddParameter("FILEPATH",file);
cmd.AddParameter("CREDENTIAL", Credential);            
cmd.AddParameter("CONFIGURATION","http://schemas.microsoft.com/powershell/Microsoft.PowerShell" );
ps.Commands = cmd;                
Runspace runSpace = RunspaceFactory.CreateRunspace();
runSpace.Open();
ps.Runspace = runSpace;
psObjects = ps.Invoke();

Answer 1

这种情况下的典型问题是您在 PowerShell 中为 32 位或 64 位版本的 PowerShell 但不是两者都运行了 Set-ExecutionPolicy。您正在运行的 C# 程序可能是您尚未更改 PowerShell 的默认执行策略的位。尝试同时打开 32 位和 64 位 PowerShell 会话，并确保将执行策略设置为 RemoteSigned 或 Unrestricted。

Answer 2

尝试使用 PowerShell 实例设置和获取 Set-ExecutionPolicy Unrestricted。

 public static ICollection<PSObject> RunScriptText(string scriptFullPath, ICollection<CommandParameter> parameters = null)
        {
            var runspace = RunspaceFactory.CreateRunspace();
            runspace.Open();
            var pipeline = runspace.CreatePipeline();

            using (PowerShell PowerShellInstance = PowerShell.Create())
            {
                var initial = InitialSessionState.CreateDefault();
                Console.WriteLine("Importing ServerManager module");
                initial.ImportPSModule(new[] { "ServerManager" });

                PowerShellInstance.Runspace = runspace;

                PowerShellInstance.AddScript("Set-ExecutionPolicy Unrestricted");
                PowerShellInstance.AddScript("Get-ExecutionPolicy");
                PowerShellInstance.Invoke();

                var cmd = new Command(scriptFullPath);
                if (parameters != null)
                {
                    foreach (var p in parameters)
                    {
                        cmd.Parameters.Add(p);
                    }
                }
                pipeline.Commands.Add(cmd);
                var results = pipeline.Invoke();
                pipeline.Dispose();
                runspace.Dispose();
                return results;
            }
            return null;
        }