WPF Binding Failure performance hit vs Exception

Posted by Aran Mulholland on Stack Overflow See other posts from Stack Overflow or by Aran Mulholland
Published on 2010-04-07T00:11:34Z Indexed on 2010/04/07 0:13 UTC
Read the original article Hit count: 738

Filed under:
|
|
|

when we bind to heterogeneous collection of objects, not all objects have the same set of properties. in the output window we get a message like:

System.Windows.Data Error: 39 : BindingExpression path error: 'RoundingFactor' property not found on 'object' ''MultiLineTextMarkingScheme' (HashCode=7262386)'. BindingExpression:Path=RoundingFactor;..........

This doesn't appear to be an exception, but we are concerned it has a performance impact.

Should we be concerned and create a view model that has all the properties we wish to bind to (and have the properties that dont exist on the underlying element return null) or can we just leave it.

This situation often occurs in a grid scenario where there might be large numbers of these binding failures.

© Stack Overflow or respective owner

Related posts about wpf

Related posts about databinding