Why are .NET property wrappers bypassed at runtime when setting dependency properties in XAML?

by

The explanation is given in XAML Loading and Dependency Properties:

The current WPF implementation of its XAML processor is inherently
dependency property aware. The WPF XAML processor uses property system
methods for dependency properties when loading binary XAML and
processing attributes that are dependency properties. This effectively
bypasses the property wrappers. When you implement custom dependency
properties, you must account for this behavior and should avoid
placing any other code in your property wrapper other than the
property system methods GetValue and SetValue.

and:

For implementation reasons, it is computationally less expensive to
identify a property as a dependency property and access the property
system SetValue method to set it, rather than using the property
wrapper and its setter. This is because a XAML processor must infer
the entire object model of the backing code based only on knowing the
type and member relationships that are indicated by the structure of
the markup and various strings.

More Related Contents:

  1. How do I use WPF bindings with RelativeSource?
  2. What’s the difference between StaticResource and DynamicResource in WPF?
  3. ResourceDictionary in a separate assembly
  4. In WPF, what are the differences between the x:Name and Name attributes?
  5. Image UriSource and Data Binding
  6. My images are blurry! Why isn’t WPF’s SnapsToDevicePixels working?
  7. Access parent DataContext from DataTemplate
  8. Apply stroke to a textblock in WPF
  9. Bind to a method in WPF?
  10. How do I set a ViewModel on a window in XAML using DataContext property?
  11. WPF Handedness with Popups
  12. What does “{x:Static}” mean in XAML?
  13. DataTrigger not firing
  14. Remove Highlight Effect from ListViewItem
  15. Binding in a WPF data grid text column
  16. wpf bind to indexer
  17. Is there a WPF Cheat Sheet available? [closed]
  18. Difference between TargetType=”controlType” and TargetType=”{x:Type controlType}”
  19. How to implement Balloon message in a WPF application
  20. How do I bind a Byte array to an Image in WPF with a value converter?
  21. WPF, ‘Object reference not set to an instance of an object’ in Designer
  22. How to force WPF to use resource URIs that use assembly strong name? Argh!
  23. Why does WPF support binding to properties of an object, but not fields?
  24. How to make modal dialog in WPF?
  25. the name does not exist in the namespace clr-namespace
  26. How to create a WPF Window without a border that can be resized via a grip only?
  27. Can you use the asp.net membership provider in a windows application?
  28. Can I overlay a WPF window on top of another?
  29. How can I produce a “print preview” of a FlowDocument in a WPF application?
  30. Is the CallerMemberName attribute in 4.5 “able to be faked”?

Leave a Comment