Steps to reproduce
Connect to remote session.
Run e.g.
PS D:\dev\PowerShell_6.0.0-alpha.17-win10-win2016-x64> icm -Session $sessions {
gci env:\ | % value | select-string temp
}
## a lot of blank lines
## if I store the output to some variable and select properties explicitly, this confirms that there are actual objects
PS D:\dev\PowerShell_6.0.0-alpha.17-win10-win2016-x64>$m = icm -Session $sessions {
gci env:\ | % value | select-string temp
}
PS D:\dev\PowerShell_6.0.0-alpha.17-win10-win2016-x64>$m | % Line
C:\Users\CLOUDA~1\AppData\Local\Temp
C:\Users\CLOUDA~1\AppData\Local\Temp
C:\Users\CLOUDA~1\AppData\Local\Temp
C:\Users\CLOUDA~1\AppData\Local\Temp
C:\Users\CLOUDA~1\AppData\Local\Temp
C:\Users\CLOUDA~1\AppData\Local\Temp
# ....
Compare to result from local run
PS D:\prgs\dev\PowerShell_6.0.0-alpha.17-win10-win2016-x64> gci env:\ | % value | select-string temp
C:\Users\J8675~1.STE\AppData\Local\Temp
C:\Users\J8675~1.STE\AppData\Local\Temp
Expected behavior
Deserialized.Microsoft.PowerShell.Commands.MatchInfo should be formatted correctly.
Actual behavior
PowerShell runtime probably doesn't know how to format Deserialized.Microsoft.PowerShell.Commands.MatchInfo to the output.
Environment data
Downloaded current alpha as of today
PS D:\prgs\dev\PowerShell_6.0.0-alpha.17-win10-win2016-x64> $PSVersionTable
Name Value
---- -----
CLRVersion
PSEdition Core
PSRemotingProtocolVersion 2.3
WSManStackVersion 3.0
SerializationVersion 1.1.0.1
BuildVersion 3.0.0.0
PSVersion 6.0.0-alpha
GitCommitId v6.0.0-alpha.17
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
This doesn't work also in 5.1:
[67]: $PSVersionTable
Name Value
---- -----
PSVersion 5.1.14393.953
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.14393.953
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
Steps to reproduce
Connect to remote session.
Run e.g.
Compare to result from local run
Expected behavior
Deserialized.Microsoft.PowerShell.Commands.MatchInfoshould be formatted correctly.Actual behavior
PowerShell runtime probably doesn't know how to format
Deserialized.Microsoft.PowerShell.Commands.MatchInfoto the output.Environment data
Downloaded current alpha as of today
This doesn't work also in 5.1: