title: What are drawbacks of creating a dependency property?
body: <p>It is said here:</p>
  <p><a href="http://msdn.microsoft.com/en-us/library/ms753358.aspx" rel="nofollow noreferrer">http://msdn.microsoft.com/en-us/library/ms753358.aspx</a></p>
  <blockquote>
  <p>Sometimes, the typical technique of backing your property with a private field is adequate.</p>
  <p>However, you should implement your property as a dependency property whenever you want your property to support one or more of the following WPF capabilities ...</p>
  </blockquote>
  <p>If I look at all the capabilities they are very obvious needs so I can't really see when I should NOT create dependency property.</p>
  <p>So if I systematically create a dependency property instead of just creating a private field what would be the drawbacks?</p>