'dotnet pack -o .' places NuGet packages in project folder

Steps to reproduce

dotnet pack -o . src\project\project.csproj

Expected behavior

NuGet packages are placed in current folder as specified with -o . This worked properly using preview2 tooling (1.0.0-preview2-003131) and project.json.

Actual behavior

NuGet packages are placed in src\project.

Environment data

dotnet --info output: .NET Command Line Tools (1.0.0-preview3-004056)

Product Information: Version: 1.0.0-preview3-004056 Commit SHA-1 hash: ccc4968bc3

Runtime Environment: OS Name: Windows OS Version: 10.0.14393 OS Platform: Windows RID: win10-x64

[eerhardt]

I just hit this as well with dotnet publish -o. My opinion is the CLI should be taking relative paths and making them into full paths relative to the current working directory, then passing that into MSBuild.

Every command-line application I am familiar with uses paths relative to the current working directory. Not relative to some arbitrary file it is operating on.

One last thing, if we ship 1.0 like this, it will be a breaking change to fix it the right way afterwards.

[nguerrera]

I think it makes sense for direct msbuild invocation and dotnet.exe invocation to differ here. In the msbuild case, there is an explicit /p argument, and so it seems reasonable that this works as it always has. But the help for dotnet -o says:

  -o|--output <OUTPUT_DIR>            Directory in which to place outputs

From that alone, it is more surprising that -o . does what it currently does.