When should I use FrameworkPropertyMetadata or UIPropertyMetadata over plain PropertyMetadata?

wpf attached-properties attachedbehaviors
Roger Lipscombe picture Roger Lipscombe · Mar 21, 2010 · Viewed 22.1k times · Source

When looking at sample attached properties and behaviors, I've seen a mishmash of uses of FrameworkPropertyMetadata, UIPropertyMetadata and PropertyMetadata. Since they all form an inheritance hierarchy, how do I choose which one to use?

Answer

gp. picture gp. · Mar 21, 2010

These classes are to report some behavior aspects of a dependency property.

Check the different classes for the options they provide.

For example,

if you just want to back a property by dp and provide a default value, use PropertyMetadata,

if you want to specify animation behavior, use UIPropertyMetadata,

but if some property affects wpf framework level stuffs eg element layout, parent layout or databinding, use FrameworkPropertyMetadata.

Details you can check on msdn http://msdn.microsoft.com/en-us/library/ms751554.aspx

Related questions

Reducing boilerplate code in MVVM WPF app for attached properties, commands, etc?

I'm working on a WPF MVVM application. The thing that I'm noticing is that I have to write an inordinate amount of boilerplate code just to declare commands (through DelegateCommands from the WPF Team's MVVM Toolkit), attached properties and attached …

Read More
What does InitializeComponent() do, and how does it work in WPF?

What does InitializeComponent() do, and how does it work in WPF? In general first, but I would especially be interested to know the gory details of order of construction, and what happens when there are Attached Properties.

Read More
Change Canvas.Left property in code behind?

I have a rectangle in my XAML and want to change its Canvas.Left property in code behind: <UserControl x:Class="Second90.Page" xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" …

Read More