Investigate configuration behavior when the values (Configurations/Platforms/TargetFrameworks) are conditioned or duplicated. #1829
Currently the expectation is that the values are only once in the project and unconditioned (since they are usually what you use as a condition). Now consider the following cases:
Values defined in a conditioned property group
Values with a specific condition
Values defined more than once
When reading the values to populate the dimensions they are populated based on the evaluated values so all these cases are covered. When writing them however it's using the construction model (since values coming from targets can't be written on top of) and picking the first value from the construction model which ignores conditions and duplicated values.
We could change the saving part use the evaluation model if the property is coming from the project and not an import. There are some design issues to take into account with this approach:
All of this behavior may or may not be desirable as this is uncharted territory.
The text was updated successfully, but these errors were encountered: