What are the reasons / scripts for properties such as DisplayMemberPath for dependency properties?

Question

Can someone explain the argument that sayControl.DisplayMemberPath has a dependency property, not just a regular CLR property?

Are there real life scenarios when such properties are used in data binding scripts, styles, or other dependency situations.

Thank.

Update:

The reason for this question is statements such as

Creating dependency on your property ownership is not always necessary or will depend on your need. Sometimes a typical technique is to support your property with a private field.

in the MSDN documentation , which make-control developers make declarations of dependency properties that do not have clearly identifiable benefits to the dependency property. private field is adequate.

Answer 1

. , ( ). - , DP, , -, /, .. ; , , .., , .

3'rd , Sync-fusion; Binding . :

wpf CLR ?

DP, - (WPF Controls), DP; , ( Binding, styling ..), .

Answer 2

DisplayMemberPath, , , , ...

, DataGrid, , DisplayMemberPath ViewModel.

.