Just code: WPF - order is matter (especially with DependencyProperty)

Wednesday, December 05, 2007

WPF - order is matter (especially with DependencyProperty)

What's wrong with following code:

class aaa : DependencyObject { }

class bbb : DependencyObject
    {
        static readonly bbb b = new bbb();
        public static bbb GetMe { get { return b; } }
        public static readonly DependencyProperty MyPropertyProperty =
            DependencyProperty.Register("MyProperty", typeof(aaa), typeof(bbb), new UIPropertyMetadata(default(aaa)));

        private bbb()
        {
            MyProperty = new aaa();
        }
        public aaa MyProperty
        {
            get { return (aaa)GetValue(MyPropertyProperty); }
            set { SetValue(MyPropertyProperty, value); }
        }
    }

Nothing special, One DependencyObject, that implement singleton pattern. You should call GetMe to create and get an instance and then use it.

Well, this code throws "Value cannot be null. Parameter name: dp" exception. Why this happens? Why class aaa can not be null? It can - it dependency object!

How to fix it? Just move registration of DependencyPropery above initialization of static bbb to solve it. Like this

class aaa : DependencyObject { }

class bbb : DependencyObject
    {
        public static readonly DependencyProperty MyPropertyProperty =
            DependencyProperty.Register("MyProperty", typeof(aaa), typeof(bbb), new UIPropertyMetadata(default(aaa)));
        static readonly bbb b = new bbb();
        public static bbb GetMe { get { return b; } }
        private bbb()
        {
            MyProperty = new aaa();
        }
        public aaa MyProperty
        {
            get { return (aaa)GetValue(MyPropertyProperty); }
            set { SetValue(MyPropertyProperty, value); }
        }
    }