dotnet publish places output in sub-directory of the app output by default

[DamianEdwards]

Steps to reproduce

Create an ASP.NET Core application in VS then publish it using dotnet publish

Expected behavior

The output of publish doesn't impact the files contained in the folder of my running app

Actual behavior

The output of publish is now included in the folder that my app runs from when I dotnet run. Depending on the what the application does, this could result in clashes with content already in the app, etc.

Environment data

dotnet --info output:

.NET Command Line Tools (1.0.0-rc2-002426)

Product Information:
 Version:     1.0.0-rc2-002426
 Commit Sha:  08ee6dedd9

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

[TheRealPiotrP]

@DamianEdwards changing this would be a breaking change for the toolset, something we're avoiding until RC2 ships.

@blackdwarf this needs design. I believe you have a doc on the output of build / publish. Can you work with @DamianEdwards and make sure concerns are covered?

[DamianEdwards]

We were thinking we'd change the default to "/bin/publish-{configuration}" instead.

What do you mean by breaking change for the toolset? Which toolset?

[HughWarrington]

Still an issue today.