<p>When using resources such as brushes, templates and styles in WPF, they can be specified either as StaticResources </p>

<pre><code>&lt;Rectangle Fill="{StaticResource MyBrush}" /&gt;
</code></pre>

<p>or as a DynamicResource</p>

<pre><code>&lt;ItemsControl ItemTemplate="{DynamicResource MyItemTemplate}"  /&gt;
</code></pre>

<p>Most of the times (always?), only one works and the other will throw exception during runtime. But I'd like to know why:</p>

<ul>
<li>What is the main difference. Like memory or performance implications</li>
<li>Are there rules in WPF like "brushes are always static" and "templates are always dynamic" etc.?</li>
</ul>

<p>I <strong>assume</strong> the choice between Static vs Dynamic isn't as arbitrary as it seems... but I fail to see the pattern.</p>

A
StaticResource
will be resolved and assigned to the property during the loading of the XAML which occurs before the application is actually run. It will only be assigned once and any changes to resource dictionary ignored.
A
DynamicResource
assigns an Expression object to the property during loading but does not actually lookup the resource until runtime when the Expression object is asked for the value. This defers looking up the resource until it is needed at runtime. A good example would be a forward reference to a resource defined later on in the XAML. Another example is a resource that will not even exist until runtime. It will update the target if the source resource dictionary is changed.