Question

While most code samples around the net use a static declaration of DependencyProperties, I found in some cases they are defined as public readonly instance members.

Are there any pros in defining a DependencyProperty as an instance-member (and not static)?

(Note: I dont want to get in the question of whether or not static members are good or bad, rather more specifically on the behaviour of the DependencyProperty object)

Answer 1

That is not quite a good idea. As soon as there is more than one instance of the control an exception should be thrown as the same property is being registered again and the registration is per-type and not per-instance.

‘X’ property was already registered by ‘Y’.

Possibly a slip by the coder in the cases you encountered.