`Configuration` property shouldn't be read in Directory.Build.props

[Youssef1313]

It's too early to read Configuration in Directory.Build.props without a workaround to set it manually to Debug when not set.

I think it's best to avoid reading the properly that early altogether. See also dotnet/msbuild#12792

[eiriktsarpalis]

What's the recommended workaround? Move to Directory.Build.targets or something different?

[Youssef1313]

I tried to move to Directory.Build.targets but didn't work, I didn't investigate why though.

[lntutor]

I am working on this. The key is to split the path setup by evaluation phase: keep configuration-independent BaseOutputPath/BaseIntermediateOutputPath values in the root Directory.Build.props, let MSBuild append the now-initialized configuration to OutputPath/IntermediateOutputPath, and define the package/test-result paths in a root Directory.Build.targets. The existing src/Directory.Build.targets must import the root targets (as src/Directory.Build.props already does for the root props), otherwise it shadows them. I will verify both Debug/Release property evaluation plus solution build, pack, and test behavior.