Proc.Start Arguments breaking change since 0.6.x upgrade to 0.8.x

[kachalkov]

hi, we have upgraded to latest version and none of the arguments are being passed in fully due to the code which tries to split by space and add to the list.

we are using bcp process to start and pass args....

[oleg-razvaliaev]

Yes. the problem exists for arguments passed in as a single string.
Example:
something.exe "argument1 passed as parameters in quoted string" argument2 argument3
Argument2 is not passed into something.exe

[Mpdreamz]

Sorry to hear!

I tried reproducing this to no avail here: #17

Can you share how you are invoking Proc and the TFM you run under?

For netstandard2.1 we don't do any argument mutations and simply pass the arg string array to: https://learn.microsoft.com/en-us/dotnet/api/system.diagnostics.processstartinfo.argumentlist?view=net-8.0&viewFallbackFrom=netframework-4.8.1

For netstandard2.0 we don't split by spaces string[] we naively quote any item in that array that has spaces.