x:Bind uses DependencyObject.SetValue instead of the C# setter

[jeromelaban]

Originally posted by @mcNets in #9876

For performance reasons, to avoid type casting, the x:Bind engine in Uno is using explicit DependencyObject.SetValue when setting the target property value, where WinUI uses the C# property setter instead.

We may not change this behavior, unless this becomes problem, as performance is a more important concern at this time.

[christianfo]

This might warrant a spot on the list of common issues. I could not find it there. The problem with these small differences between WinUI3 and Uno is that any one of them taken separately is not a big deal, but together, they add up and make the process of moving an app to Uno more tedious than it could be in my opinion. A comprehensive list of known differences would go a long way to help the process.

[jeromelaban]

This is fair. Those differences are for scattered around issues, though an issue marked as an epic would help around those differences, or maybe a tag, or directly in the common issues list as you suggested.