[Closed] Have Cook Commandlet output go to stdout?
We are currently experimenting with using the
The commandlet is run from a CMD shell on Windows but right after starting it does open its own console window where it displays its output. Since we are running it from a command line environment such as a build server we want it to output directly to the initial stdout channel instead of this additional console window.
Looking at the
Is there a way to disable this highly undesirable behaviour? There is no need to open an additional console window when already launched from a command line shell. Also, many build environments do actually not allow windows to be opened (when run as services for instance on Windows) so I suspect that this might cause issues in these cases.
The question has been closed Jul 13 '16 at 07:59 PM by Samantha Sutton for the following reason:
The question is answered, right answer was accepted
This works in C#, you could write your own wrapper that handles output as you want (in this case it directs it to Log, after the invoke which would probably be needless in a simple console app.
answered Jan 20 '16 at 12:56 AM
Follow this question
Once you sign in you will be able to subscribe for any updates here