Who has the best metaphor for WPF dependency properties?

Dependency properties are just like normal properties except they have some special "hooks" that WPF uses.

Dependency properties are just like normal properties except they have some special "hooks" that WPF uses. One special thing is that sometimes if you don't set a property value it will receive its value from the control it is placed in (so if you set the font for a button the text block inside the button will use this font unless you specified a different font for the text block), I assume this is the source of all the "never know the value" nonsense. If you are writing a WPF control you probably should use dependency properties because you can specify if changes should automatically cause the control to re-render itself (and more) and you can use them for data binding.

If you are writing a class derived from Freezable (directly or indirectly) using only dependency properties will save you some work. If you are writing a class that is not WPF specific then there is probably no reason to use dependency properties.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.