In most common WPF and XAML applications, you don't often find yourself needing to animate a resource. Generally you define resources (such as brushes) so that you can share them among multiple elements in the XAML file, and it's not often necessary to animate something that's shared in this way. Moreover, if you really wanted to animate the shared brush, you could do so indirectly through one of the elements that use that brush. However, there are cases where you need to define an object as a resource not because you need to share that object, but because you can't put that object directly in the markup. The resource is then referenced by an element in markup through a data binding. If you then need to animate that resource, some special considerations come into play. For example, suppose you wanted to create a graphical animation of a Polyline that looks something like this: CurlAround.xbap The actual pattern isn't important: What's probably obvious is that a bunch of points in a PointCollection
Read More...