|
#1
|
|||
|
|||
Interesting, I believe it has always worked this way -- it's actually due to the fact that the CreateProcess API writes its output to the current console window if STARTF_USESTDHANDLES is not specified in STARTUPINFO. In v10, the handle is specified with output none to allow this.
|
#2
|
|||
|
|||
This had an unintended side effect of suppressing output and prompts (for instance, with a pause statement in a batch file). In the latest release, you'll need to set
Application.Options.AlwaysCaptureConsoleOutput = True in a Run Script step so that the handle is specified with output none. |
|
|