Details
This is a great tool! One thing that would help me for my current use case would be if there was another event fired when a command has completed. I *think* that should probably be the "Exited" event (or perhaps "Disposed"), but admittedly I haven't tested it yet.
What I am hoping to be able to do is call some cmdline tools (such as nipkg.exe) and be able to report StdOut & StdErr as the command is executing, then detect when it is complete. I don't see a way to tell that a command has finished in the current implementation (short of matching patterns in StdOut/StdErr, which is problematic if you can't predict all possible errors ahead of time). I definitely don't want to have to wait for a timeout.
Please sign in to leave a comment.