Reply to thread

Message

<blockquote data-quote="samuel337" data-source="post: 55420" data-attributes="member: 10347">I would suggest letting the process run in the background instead of using WaitForExit like you are now because this will freeze up the UI thread (although the command output will continue to work).Add in this line when you setup the ProcessStartInfo object:psi.EnableRaisingEvents = true;Remember to subscribe to the Exited event handler of the process object (e.g. ConvertProcess). Do not WaitForExit.Now when one process has finished, the exited event handler will trigger, and you can load the next one. I'd use an enum to keep track of which step the process is at. Also, make sure you reinstantiate your process object everytime you use it.What's wrong with the current code btw (apart from what I've pointed above)? It should run each application one after the other, given you've used WaitForExit.Sam[/code]</blockquote>

[QUOTE="samuel337, post: 55420, member: 10347"] I would suggest letting the process run in the background instead of using WaitForExit like you are now because this will freeze up the UI thread (although the command output will continue to work). Add in this line when you setup the ProcessStartInfo object: psi.EnableRaisingEvents = true; Remember to subscribe to the Exited event handler of the process object (e.g. ConvertProcess). Do not WaitForExit. Now when one process has finished, the exited event handler will trigger, and you can load the next one. I'd use an enum to keep track of which step the process is at. Also, make sure you reinstantiate your process object everytime you use it. What's wrong with the current code btw (apart from what I've pointed above)? It should run each application one after the other, given you've used WaitForExit. Sam [/code] [/QUOTE]

Verification