Prerequisites

• Write a descriptive title.
• Make sure you are able to repro it on the latest released version
• Search the existing issues.
• Refer to the FAQ.
• Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Summary

This is a sub-issue of #25242.

ConvertTo-Csv and Import-Csv do not respect an explicit $false value for the -UseCulture switch parameter.

-UseCulture:$false doesn't behave as if the switch wasn't specified. It also doesn't behave as if it was specified. Instead, it results in either no delimiter (ConvertTo-Csv) or a space as the delimiter (Import-Csv).

Steps to reproduce

ConvertTo-Csv:

[pscustomobject] @{ H1 = 'V1'; H2 = 'V2' } | ConvertTo-Csv -UseCulture:$false

Export-Csv:

$file = (New-TemporaryFile).FullName
[pscustomobject] @{ H1 = 'V1'; H2 = 'V2' } | Export-Csv -LiteralPath $file -UseCulture:$false

Expected behavior

ConvertTo-Csv:

"H1","H2"
"V1","V2"

Export-Csv:

"H1","H2"
"V1","V2"

• -UseCulture:$false behaves as if the switch wasn't specified.
• The default , item delimiter is used by both commands.

Actual behavior

ConvertTo-Csv:

"H1""H2"
"V1""V2"

Export-Csv:

"H1" "H2"
"V1" "V2"

• -UseCulture:$false neither behaves as if the switch was or wasn't specified.
• ConvertTo-Csv output includes no item delimiter.
• Export-Csv output includes a space as the item delimiter.

Environment data

Name                           Value
----                           -----
PSVersion                      7.6.0-preview.5
PSEdition                      Core
GitCommitId                    7.6.0-preview.5
OS                             Microsoft Windows 10.0.19045
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0, 5.0, 5.1…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0