system.diagnost ics.process OutputDataRecei ved not quite firing

[ice9]

I seem to be missing something in this straightforward example.. but i
have a vbs file that is now simplified to one line:
Wscript.Echo "test"

When i run the process, i'd like output to be returned asynchronously
since i will be running this script many times with differetn
parameters and collecting return strings.
my return "test" text actually work in synchronous mode:
process.Standar dOutput.ReadToE nd()

however in the following example, ( inside a webservice method ), the
OutputDataRecei ved never fires:

Process p = new Process();
p.OutputDataRec eived += new
DataReceivedEve ntHandler(p_Out putDataReceived );
p.ErrorDataRece ived += new
DataReceivedEve ntHandler(p_Err orDataReceived) ;
p.StartInfo.Fil eName = @"c:\windows\sy stem32\cscript. exe";
p.StartInfo.Arg uments = @"c:\test.vb s";
p.StartInfo.Red irectStandardOu tput = true;
p.StartInfo.Red irectStandardEr ror = true;
p.StartInfo.Use ShellExecute = false;
p.StartInfo.Cre ateNoWindow = true;
p.Start();
p.WaitForExit() ;

// this works
// Process.Start(t riggerPaths);
}

void p_ErrorDataRece ived(object sender, DataReceivedEve ntArgs e) {
string s = e.Data.ToString ();
}

void p_OutputDataRec eived(object sender, DataReceivedEve ntArgs e) {
// never fires
string s = e.Data.ToString ();
}

[Willy Denoyette [MVP]]

"ice9" <so*******@gmai l.comwrote in message
news:11******** *************@h 3g2000cwc.googl egroups.com...

>I seem to be missing something in this straightforward example.. but i
have a vbs file that is now simplified to one line:
Wscript.Echo "test"

When i run the process, i'd like output to be returned asynchronously
since i will be running this script many times with differetn
parameters and collecting return strings.
my return "test" text actually work in synchronous mode:
process.Standar dOutput.ReadToE nd()

however in the following example, ( inside a webservice method ), the
OutputDataRecei ved never fires:

Process p = new Process();
p.OutputDataRec eived += new
DataReceivedEve ntHandler(p_Out putDataReceived );
p.ErrorDataRece ived += new
DataReceivedEve ntHandler(p_Err orDataReceived) ;
p.StartInfo.Fil eName = @"c:\windows\sy stem32\cscript. exe";
p.StartInfo.Arg uments = @"c:\test.vb s";
p.StartInfo.Red irectStandardOu tput = true;
p.StartInfo.Red irectStandardEr ror = true;
p.StartInfo.Use ShellExecute = false;
p.StartInfo.Cre ateNoWindow = true;
p.Start();
p.WaitForExit() ;

// this works
// Process.Start(t riggerPaths);
}

void p_ErrorDataRece ived(object sender, DataReceivedEve ntArgs e) {
string s = e.Data.ToString ();
}

void p_OutputDataRec eived(object sender, DataReceivedEve ntArgs e) {
// never fires
string s = e.Data.ToString ();
}

You have to start an asynchronous read of both standarderror and standardoutput before
calling WaitForExit.
Search the docs for BeginOutputRead Line etc...

Willy.