Hello,
I have stumbled upon something interesting and that is the ability to register a dependencyproperty with the ownerType FrameworkElement even though the class which contains the dependencyproperty is not FrameworkElement. Furthermore the dependencyproperty is not even an ATTACHED one.
Why does such behavior works? What is happening behind such dp registration?
I know I should usually define a dp with the ownerType of class which also contains the depencencyproperty but I am asking this to figure out why is this extraordinary case working and whats happening under the hood?
This is an example from http://social.msdn.microsoft.com/Forums/en-US/wpf/thread/28f1754e-378b-4717-b4f4-20bdbc6ff095
In this example the class DependencyProperties defines a dp with ownerType FrameworkElement. Mr. Josh Smith suggested to use FrameworkElement as ownerType, why so?
publicclassDependencyProperties
{
private DependencyProperties() { }
publicstaticreadonlyDependencyProperty MyPropertyProperty =
DependencyProperty.Register(
"MyProperty",
typeof(string),
typeof(FrameworkElement),
newFrameworkPropertyMetadata(
"this is the default value",
FrameworkPropertyMetadataOptions.Inherits));
}
What is happening behind a dependencyproperty registration?
Anybody had the same problem?