You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
changing the Path to "Hue2" causes a compiler error as expected.
I don't know if this is a compiler bug or whether this is information missing in the documentation similar to the note saying "Compiled bindings are disabled for any binding expressions that define the Source property. This is because the Source property is always set using the x:Reference markup extension, which can't be resolved at compile time"
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
ID: d8079bc8-3987-9069-717e-c5cbf3512ae1
Version Independent ID: d8079bc8-3987-9069-717e-c5cbf3512ae1
I've chatted to the engineers and as you've identified, compiled bindings don't work with multi-bindings. Therefore I'll update the doc with a note to that effect.
The engineers have an issue to add compiled bindings support to multi-bindings, but it's not something that will happen in the short term.
If you add the following label to the StackLayout in the "Use compiled bindings" section
and then change e.g. "Hue" to "Hue2" as binding path, the file still compiles.
On the other hand with the verbose writing method of a normal binding
changing the Path to "Hue2" causes a compiler error as expected.
I don't know if this is a compiler bug or whether this is information missing in the documentation similar to the note saying "Compiled bindings are disabled for any binding expressions that define the Source property. This is because the Source property is always set using the x:Reference markup extension, which can't be resolved at compile time"
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: