Start-Process output stream.
Hi
Is there any reason why the below executable would not produce any output
Write-host test in Debug
echo $env:path
Start-Process -NoNewWindow -Wait -FilePath .\cpp\vs2013\Debug\ISO-8583-DTT-Testd.exe -Args "-all"
while the same executable on my Win7 is producing this output
PS Z:\git\ISO-8583> Start-Process -NoNewWindow -Wait -FilePath .\cpp\vs2013\Release\ISO-8583-DTT-Test.exe -Args "-all"
testInputStream:
testOutputStream:
testInputOutputStream:
testAlphabetic:
testAlphaNumeric:
testAlphaNumericSpecial:
testStream:
testNumeric:
testSignedNumeric:
testBitmaps:
testLLAlphabeticTest:
testStream:
testLLAlphaNumericSpecial:
testLLLAlphaNumeric:
testStream:
testLLNumeric:
testLLNumericStringStream:
OK (17 tests)
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac

Support Staff 1 Posted by Feodor Fitsner on 01 Dec, 2015 06:09 PM
Well, AppVeyor "console" is not the same as running an app in your local console. In some cases AppVeyor can't catch the output, especially if the app uses direct console API.
Start-Processcmdlet can redirect output to a file. You can redirect to some temp file and then just output its contents to the build console (or put that file to artifacts).Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 02:02 AM.