Vista - Running an external process asynchronously

Hi all,
All the question is in the title;

I need to run an external process from my powershell script asynchronously,
I want powershell to continue my script execution as soon as this process is
started.

Any idea?

Thanks in advance

Romu wrote:PowerShell v1:
http://jtruher.spaces.live.com/blog/...628D!130.entry

PowerShell v2 CTP1/CTP2:
get-help start-psjob

Marco

--
Microsoft MVP - Windows PowerShell
http://www.microsoft.com/mvp

PowerGadgets MVP
http://www.powergadgets.com/mvp

Blog:
http://marcoshaw.blogspot.com

"Romu" <Romu@xxxxxx> wrote in message
news:26878AEF-39AC-412F-96A3-5BB7775BC0B0@xxxxxxIf you are willing to give the PowerShell Community Extensions a try, you
can use Start-Process like so:

foo.ps1
--------
echo "Before"
Start-Process csc.exe -arg '/?' -noshellexecute
echo "!!!!! After !!!!!"

--
Keith Hill
http://www.codeplex.com/powershellcx

Many thanks guys,
Indeed I just realized that the thing I need to call asynchronously is a
powershell function of my own.

An example :
#The function
function Synchronise(computername)
{
....
}


#The script
Synchronise(PC1)
Synchronise(PC2)
Synchronise(LINUX1)
Synchronise(MAC1)


My function Synchronise is called several times and I need to run
asynchronously. This function is used to synchronise a set of files and
folders on computers and it's called several times because we synchronise
several computers.

I would like to see the script to continue once the synchronisation is
launched.

Thanks in advance for your help.

romu

"Keith Hill [MVP]" wrote:

Romu wrote:Yup, the solutions Keith and I proposed could be embedded within your
functions. The only thing not evident to me (this early in the morning
;-)) is if you expected to somehow return the results from the function.

I can't think of another easier way for you to attempt what you want.

Marco

Thanks for quick answer Marco,
No the function doesn't return any result, it is just a "run and forget"
function.

And I can't make the inside aynchronous as the actions performed by the
function must be sequential. So the whole function must be aynschronous.

"Marco Shaw [MVP]" wrote:

Romu wrote:Perhaps Keith and I are missing something... First, what solution are
you willing/wanting to try out, and we will go from there:

#1: v1: Use Jim's background jobs.
#2: v1/v2 CTP: Use Keith's PSCX.
#3: v2 CTP: Use *-PSJobs

If in a prod environment, and you can't go installing 3rd party
PowerShell add-ons, then it seems #1 is your option. It is just some
PowerShell scripts that use existing functionality provided by
PowerShell v1.

Marco

Thanks Marco,
I've just taken a look at the jim's background jobs and I think this is what
I need.

Thanks for your help.

"Marco Shaw [MVP]" wrote: