Using Get-Content -AsByteStream
, one can read file as a byte stream.
Using Set-Content -AsByteStream
, one can create a file from a byte stream.
However, I haven't found a way to pass these byte streams to other non-PowerShell commands. Pipes between external commands always decode the data as a string, which mangle binaries.
cmd /c --%
or Start-Process -RedirectStandardInput
do solve part of the problem, but it can get a bit tedious if any of involved commands is another cmdlet. Is there a PowerShell-native way to handle executable input/output as a stream of byte?