Repository navigation
Configuration property shouldn't be read in Directory.Build.props #995
Description
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
Activity
eiriktsarpalis commentedon Nov 20, 2025
What's the recommended workaround? Move to Directory.Build.targets or something different?
Youssef1313 commentedon Nov 20, 2025
I tried to move to Directory.Build.targets but didn't work, I didn't investigate why though.
lntutor commentedon Jul 30, 2026
I am working on this. The key is to split the path setup by evaluation phase: keep configuration-independent
BaseOutputPath/BaseIntermediateOutputPathvalues in the rootDirectory.Build.props, let MSBuild append the now-initialized configuration toOutputPath/IntermediateOutputPath, and define the package/test-result paths in a rootDirectory.Build.targets. The existingsrc/Directory.Build.targetsmust import the root targets (assrc/Directory.Build.propsalready does for the root props), otherwise it shadows them. I will verify both Debug/Release property evaluation plus solution build, pack, and test behavior.