Managing Processes in PowerShell

re: Managing Processes in PowerShell

Nico — Wed, 04 Nov 2009 04:48:43 GMT

Hi.

I got a master powershell script calling a subscript. The subscript throw an error but $LASTEXITCODE in MASTER doesn't seem to catch it.

Basically my process stops at the time the throw command is run and the process is not returned to MASTER.

Is there a way around this?

re: Managing Processes in PowerShell

Marc Magnin — Wed, 29 Jul 2009 16:37:51 GMT

Thanks a lot for this article !

-marc

re: Managing Processes in PowerShell

Chris Patti — Wed, 29 Jul 2009 01:48:00 GMT

It would be really great to see an updated version of this with all of the V2 extensions like Start-Process and the Jobs extensions.

Thanks for all the hard work, PowerShell is shaping up to be one truly amazing tool for process automation!

-Chris

Re: how to create syncronous commands

Latest Newsgroup Posts — Sun, 19 Aug 2007 21:30:21 GMT

You can find more details here: [link] Shay [link]

Re: need to wait for command execution

Latest Newsgroup Posts — Sun, 03 Jun 2007 23:06:55 GMT

A short google search got: < [link] > where the tip to pipe output to out-null is given. notepad

re: Managing Processes in PowerShell

Siddartha — Sat, 28 Apr 2007 14:22:07 GMT

Actually i am integrating VB and a program written in C++. I am able to run this C++ program by clicking a button designed in VB. Once i click the button the prgram runs on the DOS platform. I do not want this DOS platform visible.But the C++ process should continue to run in the background,invisible.

re: Managing Processes in PowerShell

Nisai Wanakule — Fri, 20 Apr 2007 07:49:21 GMT

If I pass the scriptblock that contain variable, the code doesnot seem to work. This is because child process doesnot inherit the variables from the parent. How can I overcome this?

re: Managing Processes in PowerShell

Adrian Milliner — Mon, 22 Jan 2007 20:14:44 GMT

Bruce, I've been playing around with runspaces to achieve background processing of scriptblocks (at http://ps1.soapyfrog.com/2007/01/22/running-pipelines-in-the-background/ )

Are we likely to see this becoming more friendly in upcoming releases?

I realise runspaces are really there for host applications to use, but they do seem serviceable.

Your comment on the "PowerShell connect site" is noted.

re: Managing Processes in PowerShell

PowerShell Team — Wed, 17 Jan 2007 11:30:54 GMT

"$np = get-process notepad" is *extemely* hit or miss if you use notepad alot. You could sort the processes by start date, created by you etc in an effort to mitigate errors but yeah - we should have provided a way of getting the most recent process created in a runspace. Rather than having a single $LASTPROCESS variable, I was thinking that a $process array along the lines of $error would be nice. The most recently created process would be kept in $process[0].

> as PowerShell is a shell, shouldn't process/job control be a first class citizen

That would seem obvious wouldn't it :-) I had implemented a New-Process/Start-Process cmdlet but it was cut from the project at one point. In triaging what went into V1, anything more than basic process management got a relatively low rank because PowerShell gives you have access to [Diagnostics.Process]. This means that, while it might be complex, you can do pretty much anything. To ship is to choose as Jeffrey says.

Please post a request on the PowerShell connect site so other people can mod it up. This is an important data source in the tirage process for what goes into the next version. If a sufficient number of people ask for it, then it goes on the short list for V.Next.

And, responding to an earlier comment:

> What is the powershell equivilent of launching processes on remote machines, does it still use WMI?

Remote operations in 1.0 require you to use WMI, remotable .NET APIs or other existing remoting mechanisms. PowerShell 1.0 has no explicit remote capabilities. Support for remoting is a Pri 0 for the next release.

Thanks,

-bruce

re: Managing Processes in PowerShell

Adrian Milliner — Wed, 17 Jan 2007 11:07:49 GMT

I find that:

$np = get-process notepad

is a bit hit and miss - which notepad process should it get? Worse, if there is one match, it returns a single Process object... if not, an array.

Maybe the next version of PowerShell can preload a $LASTPROCESS variable with the process object of the last process it launched, so things like:

notepad ; $LASTPROCESS.WaitForExit()

are possible.

Also, as PowerShell is a shell, shouldn't process/job control be a first class citizen and be supported with cmdlets?