dotnet run no longer passes additional arguments to application (2.0.0-preview1-005619)

[mikeharder]

Repro Steps

1. Install .NET SDK 2.0.0-preview1-005619
2. dotnet new console
3. Edit Program.cs and add Console.WriteLine(args.Length)
4. dotnet restore
5. dotnet run -- foo

Expected: 1
Actual: 0

Looking at the process tree, I can see that dotnet run is not passing the arguments to dotnet exec.

Doesn't repro on previous build 2.0.0-preview1-005488.

[eerhardt]

Doing a quick investigation, it looks like a regression with using the separator --. I ran dotnet run foo and 1 was outputted. I assume this regression came from using the new https://github.com/dotnet/CliCommandLineParser/ parser in the cli.

/cc @jonsequitur

[wli3]

(working on it)

[wli3]

[update] This branch should be able to fix the parser issue. 'foo' is in args now. However, the other functional test still cannot pass.

https://github.com/dotnet/cli/compare/master...wli3:fix-dotnetrun--foo?expand=1

I am not sure if my set up is wrong in the beginning. "MSBuildTestApp" app can take whatever args and still print hello world?