Paul Higinbotham

Removing the WG-Remoting tag because this does not involve PowerShell remoting, and appears to be a bug in PowerShell during command line debugging.

Removing WG-Remoting tag since this does not involve PowerShell remoting.

This is actually by design for `Enter-PSSession`. The argument for `Write-Output ([Environment]::MachineName)` is evaluated on the client. The evaluated argument ("server1") is then packaged with `Write-Output` and sent to the...

The argument is evaluated in the ScriptBlockToPowerShellConverter, while packaging the command to be sent over to the remote session. https://github.com/PowerShell/PowerShell/blob/master/src/System.Management.Automation/engine/runtime/ScriptBlockToPowerShell.cs#L678 I think it would be a pretty big breaking change,...

Yes, this client side evaluation was implemented on purpose. But I wasn't part of the decision at the time and can only speculate as to why this was done. So...

It looks like pipeline execution event id, `800`, was replaced with `4103` at some point. It logs the same information but the details label is slightly different (was 'Context Information:',...

Ok, I now see the 800 event data ... I was looking in the wrong place for it before. I presume this was removed from PowerShell Core because it was...

This is a response to other issues created against foreach -parallel, where there is a reasonable expectation that the script block is run in the current state. #12239

@somescout That would be ideal, but is not possible. There are too many issues. One is performance; replicating runspace state is time and resource intensive, and many times not even...

Linking in related issue: #12313