tags:

views:

578

answers:

1
+3  A: 

Methods prefixed with Begin typically run asynchronously. Is this what you want? Because it appears that the loop runs as fast as it can, calling more and more BeginOutputReadLine (because the call returns immediately, before it's done and the loop comes around for another iteration).

You could call ReadLine on the StandardOutput stream for a synchronous solution. Or:

    while ( !p.HasExited ) {
        /* ... - irrelevant */
        if ( redirect && !busy ) {
            try {
                busy = true;
                p.BeginOutputReadLine();
            } catch { }
        }
    }
   ////In the method that gets called upon completion of BeginOutputReadLine
   busy = false;

Keep this in mind though (from MSDN):

When asynchronous read operations start, the event handler is called each time the associated Process writes a line of text to its StandardOutput stream.

You can cancel an asynchronous read operation by calling CancelOutputRead. The read operation can be canceled by the caller or by the event handler. After canceling, you can call BeginOutputReadLine again to resume asynchronous read operations.

That leads me to believe you should only call this method once and it will keep notifying you through callback when a line gets written.

colithium
I believe this is the issue as well; it just occurred to me, but you already wrote it for me :)
Fredrik Mörk
That's just about what I tried, except from the try..catch - I'll add that in. Is MSDN trying to say that you only need to call BeginOutputReadLine once? Or does it need to be resumed after every line?
Lucas Jones
(Not in this question, sorry!) I need to remember what's on the inbterwebs and what's not.
Lucas Jones
It sounds like it only needs to be called once with a delegate to your method that does something whenever a line is outputted. It will just keep calling that method after you set it up each time a new line is outputted.
colithium
OK, I'm back online now so I'll try that out. Thanks.
Lucas Jones