Open rainersigwald opened 7 years ago
Ya we should fix this. This is the behavior that the property pages code has had forever and changing it is risky since it affects all projects so not for RTM but we should fix it soon after.
See the comment I made here #1300 which also falls into this bucket
@RaulPerez1 With the new config changes, what's the behavior?
Behavior will be the same, this is independent of how you handle configurations. This is controlled via the rules for the property pages with the HasConfigurationCondition value. Anything that has it set to true will end up writing conditioned values and it looks from the example above that it's giving you the full matrix of properties for that one if it's defaulted (which is what I would expect).
Okay, I agree it would be nice to do better here.
I created a new project multitargeted to
net46;netstandard1.3
. I went to project properties -> Build, selected "All Configurations" and "All Platforms", and checked the "Allow unsafe code" box. Instead of a simple unconditional addition of the propertyin the existing unconditional
PropertyGroup
, the project file change isThe former is both more succinct and easier to later extend to new configurations.