Quote Originally Posted by TnTinMN View Post
I'm not sure what you mean by secondary task, but what happens if you send a blank line after starting the process?
Code:
p.StandardInput.WriteLine(String.Empty)
Since you mentioned killing the command window and then receiving the output, it sounds as though the 3rd party app may be waiting for some type of user input.

Just a thought.

Edit: If it is looking for input, something else to try would be to try sending an EOF character (Chrw(26)).
I checked the source of the 3rd party app and its writing using printf statements (C++), so nothing special.

Writing to StandardInput certainly improves things, the redirected output appears in the window. But... I still get it in chunks a few minutes apart. I tried both versions of the code shown in this thread an dthey behave the same.

Counting the characters of one chunk, it's always 4195 which sounds suspiciously close to 4096. I guess that takes me full circle back to some kind of buffer size; it would seem the redirected output is only despatched when that buffer is full.