Allow suppressing of $(Configuration) being added to $(OutputPath)

In the .props files, we have

https://github.com/dotnet/sdk/blob/2eb6c546931b5bcb92cd3128b93932a980553ea1/src/Tasks/Microsoft.NET.Build.Tasks/targets/Microsoft.NET.DefaultOutputPaths.targets#L33-L34

This unconditionally adds $(Configuration) to the end of $(OutputPath). This prevents a Directory.Build.props file from customizing the output path to arrange all output paths first by $(Configuration) and then by $(MSBuildProjectName) under some top-level bin directory.

There is already a $(AppendTargetFrameworkToOutputPath) property that can suppress adding the target framework. Can we please add $(AppendConfigurationToOutputPath) so that we can set it to false in Directory.Build.props?

Note: it’s too late to reset the $(OutputPath) in our Directory.Build.targets file to what we want, because by then, many other properties based on $(OutputPath) have already been set, and there’s no way to exhaustively reset them all, nor would we want to.

[marcpopMSFT]

Seems like a reasonable request but below our current priority list. We’d review a PR if there was interest in contributing this.

[AArnott]

My “workaround” at present has been to give up on my preferred top-level bin directory structure. If there’s some property I can set in my Directory.Build.props file that will make this work, I’m interested. I don’t want to set it once, then set it again later to ‘override’ what the SDK does, because in the meantime other properties have “copied” that BaseOutputPath and I can’t ‘fix’ them all.