I'm looking to run some powershell scripts via automation. Something like:
IList errors;
Collection<PSObject> res = null;
using (RunspaceInvoke rsi = new RunspaceInvoke())
{
try
{
res = rsi.Invoke(commandline, null, out errors);
}
catch (Exception ex)
{
LastErrorMessage = ex.ToString();
Debug.WriteLine(LastErrorMessage);
return 1;
}
}
the problem I'm facing is that if my script uses cmdlets such as write-host
the above throws an System.Management.Automation.CmdletInvocationException
-
Cannot invoke this function because the current host does not implement it.
What are some good options for getting around this problem?
From what I can tell, the only way to invoke a PowerShell script is to use the "Open program/file" action to launch the PowerShell interpreter and to pass it the path to the script to execute.
run with a hidden window flag to launch cmd.exe /c powershel.exe -file c:\script. ps1. When powershell is called from cmd it will run in the existing cmd window which is already hidden by wscript.exe //b /nologo c:\launcher. vbs.
One option is to create a write-host function and inject that into your runspace. The function will take precedence over a cmdlet with the same name. In this function, you could do nothing or perhaps use [console]::writeline() if your app is a console app, or if your app is a GUI app, inject some object into the PowerShell session that the function can write the output to (look at Runspace.SessionStateProxy.SetVariable).
Another (bit more complicated) option is to implement the PowerShell hosting interfaces in your app.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With