Question

It seems that the PowerShell -split operator and .NET Split() method act completely different.

.NET treats separator strings as if they were character arrays.

$str = "123456789"
Write-Host ".NET Split(): "
$lines = $str.Split("46")
Write-Host "Count: $($lines.Length)"
$lines

$str = "123456789"
Write-Host "-split operator: "
$lines = $str -split "46"
Write-Host "Count: $($lines.Length)"
$lines

Output:

.NET Split():
Count: 3
123
5
789


-split operator:
Count: 1
123456789

Is there a way to make a .NET application use the same technique as the PowerShell, and use the string separator as one solid unit? Hopefully, without RegEx.

This worked in PowerShell, using the Split():

Write-Host "Divided by 46:"
"123456789".Split([string[]]  "46", [StringSplitOptions]::None)

Write-Host "`n`nDivided by 45:"
"123456789".Split([string[]]  "45", [StringSplitOptions]::None)


Divided by 46:
123456789


Divided by 45:
123
6789

Answer 1

.NET’s String.Split method has two (groups of) overloads. The first receives a character array, and the second a string array. There isn’t actually an overload that receives a string. The first one behaves like you describe, with each character being split individually. The second splits along whole strings, like you want it to.

Due to the way PowerShell parses the parameters, a string passed to Split will be parsed as a char array, and the first overload called. If you could explicitly specify that the “46” is an array containing just one string, it should give you the behavior you want.