title: Difference between Color and SolidColorBrush clarification
body: <p>Ok this has been bugging me and I haven't really found any kind of definitive answer as the the reason/cause of the difference between <code>Color</code> &amp; <code>SolidColorBrush</code> so I'm wondering if someone can educate me on this.</p>
  
  <p>I already know the differences in usage, like for example I can use a <code>SolidColorBrush</code> in a dependency like if I say;</p>
  
  <pre><code>&lt;SolidColorBrush x:Key="BlahBrush" Color="#FFFFFFFF"/&gt;
  &lt;Border Background="{StaticResource BlahBrush}"/&gt;
  </code></pre>
  
  <p>but then say I throw the same resource in an <code>EasingColorKeyFrame</code> kind of like;</p>
  
  <pre><code>&lt;EasingColorKeyFrame KeyTime="0" Value="{StaticResource BlahBrush}" /&gt;
  </code></pre>
  
  <p>then it's going to puke at me about it being a SolidColorBrush....except then I can get around that by just declaring it via a resource chain back to a <code>Color</code> kind of like;</p>
  
  <pre><code>&lt;Color x:Key="OriginalBlahBrush"&gt;#FFFFFFFF&lt;/Color&gt;
  &lt;SolidColorBrush x:Key="BlahBrush" Color="{StaticResource OriginalBlahBrush}"/&gt;
  </code></pre>
  
  <p>and it will be just fine....but then again I could just utilize the <code>Color</code> property alone of the <code>SolidColorBrush</code> and can get the same behavior without being separated kind of like;</p>
  
  <pre><code>&lt;SolidColorBrush&gt;
       &lt;SolidColorBrush.Color&gt;
          &lt;Color A="255" R="0" G="0" B="255" /&gt;
       &lt;/SolidColorBrush.Color&gt;
  &lt;/SolidColorBrush&gt;
  </code></pre>
  
  <p>So I guess my question is, what is the inherent difference between the Colors and SolidColorBrush class's and the reason for their weird quirks in usage? aka I guess what's the reason for   System.Windows.Media.Colors vs System.Windows.Media.SolidColorBrush if they're both just giving a solid damn color?? </p>
  
  <p>Inquiring minds want to know! :) </p>