Please give an example of the context where you're reading it, and someone
might be able to give you more information.
I know of dependency properties from WPF. Here's an example: You have a
window with a content of a docking panel that has six buttons in it, and
you want to change the font on all the buttons. Changing the font of the
window will change the font of the docking panel and the button --it does
it all the way down. If you then change the font of one of the buttons
specifically, it will retain that setting even if you once again change the
font of the window.
Robin S.
--------------------------------------
"Jason Richmeier" <Ja************@discussions.microsoft.comwrote in
message news:67**********************************@microsof t.com...
>I came across a code sample in a book that I am reading that uses a
dependency property. I looked at some of the documentation for
dependency
properties but, for some reason, the concept is not clicking. Can anyone
provide an simple explanation of what they are and why I need them or
point
me to some good articles? By the way, the code sample uses one
dependency
property and other "normal" properties so the question is why is the one
a
dependency property while the others are not? What are the advantages
and
disadvantages?
Thank you,
Jason Richmeier