http://blogs.msdn.com/b/expression/archive/2010/02/22/switching-visual-states-easily-using-gotostateaction.aspxOver the next couple of weeks, it seems like a good idea to go over some of the behaviors we shipped as a part of Expression Blend 3. Many of you have mentioned that you would like to learn more about the stock behaviors we ship and how they are useden-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/expression/archive/2010/02/22/switching-visual-states-easily-using-gotostateaction.aspx#9968975Thu, 25 Feb 2010 00:55:05 GMT91d46819-8472-40ad-a661-2c78acb4018c:9968975Kirupa (MS)<p>Carl - if you have any requests, I can prioritize those higher so that you see them sooner =)</p> <p>Glad the info helped you out!</p> <p>Cheers,</p> <p>Kirupa</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=9968975" width="1" height="1">http://blogs.msdn.com/b/expression/archive/2010/02/22/switching-visual-states-easily-using-gotostateaction.aspx#9968388Wed, 24 Feb 2010 00:31:40 GMT91d46819-8472-40ad-a661-2c78acb4018c:9968388Zodman<p>You think you know how it works, and then an article like this comes along. &nbsp;I've been using this behaviour in a WPF project for some time, and had no idea what the TargetName property did. &nbsp;Now I know why; WPF controls don't have their own states exposed (like they do in Silverlight).</p> <p>I've tried simply typing the state name into the StateName property, but Blend clears it out. &nbsp;Looks like the only way is to add these states in myself. &nbsp;</p> <p>I'm looking forward to the rest of this series.</p> <p>Carl.</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=9968388" width="1" height="1">