Normal
To find out when the called program has finished, you may use the Exited Event on the Process Object or use the WaitForExit Method (as in the code above). When you know that the first process is done (and maybe the result was acceptable, e.g. no errors) you may call the 2nd prog exactly the same way.If you have 2 uses for the output of the program (e.g. one for showing the user and one for checking correctness or errors) you should consider using 2 delegates on the OutputDataReceived, one for each task. The more desktops are multi-processor environments, the more parallel we developers have to think.
To find out when the called program has finished, you may use the Exited Event on the Process Object or use the WaitForExit Method (as in the code above). When you know that the first process is done (and maybe the result was acceptable, e.g. no errors) you may call the 2nd prog exactly the same way.
If you have 2 uses for the output of the program (e.g. one for showing the user and one for checking correctness or errors) you should consider using 2 delegates on the OutputDataReceived, one for each task. The more desktops are multi-processor environments, the more parallel we developers have to think.
