Dongbo Wang (@daxian-dbw) the difference between stable and preview is deliberate as to prioritize compat for stable while ensuring we have the new desired behavior in preview to continue to get feedback. Maybe an option we can take here to make this more clear is to wrap it in a new Experimental Feature. Specifically, Windows mode is experimental.

I understand there will be difference between stable and preview versions. However, the native arg passing feature is already official, so making an official feature behave differently seems confusing.

Introducing a new experimental feature for the different arg passing behavior in preview versions sounds like a good idea. A doc issue needs to be opened for the new experimental feature.

Dongbo Wang (@daxian-dbw) We should probably advertise that Windows mode is still experimental and changes will continue until we can get to an acceptable level of compatibility

This pull request has been automatically marked as Review Needed because it has been there has not been any activity for 7 days.
Maintainer, please provide feedback and/or mark it as Waiting on Author

@PowerShell/powershell-committee Please review this PR and decide whether this PR should be closed or accepted.

@PowerShell/powershell-committee discussed this. We agreed to a new PSWindowsNativeCommandArgPassing experimental feature. When this feature is enabled:

• On Windows
  • $PSNativeCommandArgumentPassing = Windows
• Non-Windows
  • $PSNativeCommandArgumentPassing = Standard

When this feature is disabled:

• On Windows
  • $PSNativeCommandArgumentPassing = Legacy
• Non-Windows
  • $PSNativeCommandArgumentPassing = Standard

Additionally, new telemetry metric will be added for native command execution to inform the mode being used.

This PR has 24 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

Label      : Extra Small
Size       : +21 -3
Percentile : 9.6%

Total files changed: 4

Change summary by file extension:
.cs : +17 -2
.ps1 : +4 -1

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

🎉v7.4.0-preview.4 has been released which incorporates this pull request.:tada:

Handy links:

• Release Notes

So the default behavior in 7.2 is Legacy, then in 7.3 it's Windows, now it's going to be Legacy in 7.4 unless an experimental feature is enabled which makes it into Windows by default unless you set a new variable to Legacy, do I have that right?

@ImportTaste, this is marked to backport to 7.3.

@PowerShell/powershell-committee Are we okay with making this change to 7.3 after it has been release?

PS-Committee decided to make this feature stable in 7.4, so the default will be Windows in 7.4. Based on the telemetry, it seems that most Windows (like 99%) have not changed the default in 7.4 previews to Legacy or Standard. As such, there is no reason to backport to 7.3 which will be supported for just 1 more year.

it seems that most Windows (like 99%) have not changed the default in 7.4 previews to Legacy or Standard

What's the difference between Windows and Standard on Windows?