Consider leveraging OutputDataReceived event about bgprocess

[joshooaj]

I put together a sample gist that I think is about as good as it gets when you subscribe to the OutputDataReceived and ErrorDataReceived events.

The stdout and stderr streams are nicely interleaved, and I think the code is less complex than reading from these streams from separate runspaces, but because those events are only fired when a newline is observed, you may not be able to see the last line of text send to stdout until you cause the process to write a newline by writing something to stdin to answer the prompt.

Also, the timestamp of that last line is the time the line was observed by the script, which could be very different from when the line was originally written by the process.

I don't think the eventhandler route will be flexible enough to bother with, but it was a good learning exercise on working with events and the Register-ObjectEvent cmdlet.