Use RedirectStandardOutput. Sample from MSDN: // Start the child process. Process p = new Process(); // Redirect the output stream of the child process. p.StartInfo.UseShellExecute = false; p.StartInfo.RedirectStandardOutput = true; p.StartInfo.FileName = “Write500Lines.exe”; p.Start(); // Do not wait for the child process to exit before // reading to the end of its redirected stream. // … Read more
I’ve experienced this before. Sometimes, the way in which the process you’re calling outputs to the console is not compatible with this sort of output redirection. I’ve been fortunate enough in this case to be able to modify the external process to get around this. You might try running your code on another process that … Read more
Use Process.OutputDataReceived event from the process, to recieve the data you need. Example: var myProc= new Process(); … myProc.StartInfo.RedirectStandardOutput = true; myProc.OutputDataReceived += new DataReceivedEventHandler(MyProcOutputHandler); … private static void MyProcOutputHandler(object sendingProcess, DataReceivedEventArgs outLine) { // Collect the sort command output. if (!String.IsNullOrEmpty(outLine.Data)) { …. } }
Proposed solutions with BeginOutputReadLine() are a good way but in situations such as that, it is not applicable, because process (certainly with using WaitForExit()) exits earlier than async output finished completely. So, I tried to implement it synchronously and found that the solution is in using Peek() method from StreamReader class. I added check for … Read more
The System class has a setOut and setErr that can be used to change the output stream to, for example, a new PrintStream with a backing File or, in this case, probably another stream which uses your logging subsystem of choice. Keep in mind you may well get yourself into trouble if you ever configure … Read more