Why do so many wpf controls implement CLR properties instead of dependency properties?

Question

is it because control programmers are lazy, too hard to implement or not to know?

Wether are custom controls from third-party vendors or from Microsoft itself; most controls often have clr properties instead of DP. Result, I can't get attached to them and wpf is not all about binding?: /

My next question will be: why do so many wpf controls provide visual parts, but they are not part of the visual tree? see datagrid wpf columns, headers ...

What do you think?

Answer 1

, , , , :

• WPF Silverlight Windows Forms. , , , , WinForms, . , Silverlight, : , WinForms, .
• WPF, , "", WPF " " ( , , WPF , ). , , WPF, .
• , , , , , - - .
• DP CLR. , CLR collection ( "", "" "" ). FxCop . , , DP -. ( , FxCop) CLR, ( " - - GridView. Columns collection?" ).

: , .