My original vbs was intended to be more generic, that's why I didn't
want to embed it in the vbs to start (and I wanted to be more cross
platform) but I've modified it now to wait for the specific file to
exist. Note this uses Wscript as I call it with cscript.exe to make it
all nant friendly
Sam
This VBS code example is how to kill a process, but the principle is the
same - watch for it to disappear from the process list.
http://www.robvanderwoude.com/vbstech_proc_process.html
Tony
-Original Message-
From: Brass Tilde [mailto:[EMAIL PROTECTED]
Sent: Monday, November 10, 2008 9:
> the installer directly. I'm launching the process remotely, which
> requires my nant exec task to call a vbs script locally, and the vb code
> starts the process on the remote machine. The vbs script does not wait
> for the remote process started to complete before the vbs itself
> completes.
Unfortunately that will not work for me, because nant is not launching
the installer directly. I'm launching the process remotely, which
requires my nant exec task to call a vbs script locally, and the vb code
starts the process on the remote machine. The vbs script does not wait
for the remote p
Hi,
You can use / elements:
http://nant.sourceforge.net/release/latest/help/types/fileset.html
Each line in that file specifies a pattern to match files against.
Hope this helps,
Gert
From: netvampire.tw [mailto:[EMAIL PROTECTED]
Sent: maandag 10 november 2008 7:40
To: nant-
Steve,
You can spawn the installation, and then wait for it to finish.
For example:
...
Note:
You'll need a recent version of both NAnt and NAntContrib for this.
Gert
-Original Message-
From: Steve Kapinos [mailto:[EMAIL PROTECTED]
Sent: maandag 10 november
Part of my script must wait until an installation completes, but this
installation spawns off into another process, so the exec task does not
wait for it to complete before finishing and the nant script continues
to march on.
Right now for a quick hack, I have a sleep timer in the script to simply
