The team blog of the Expression Blend and Design
The Blend 2 Service Pack 1 contains a secret ingredient that can be activated by installing the WPF Toolkit and then setting a Registry value. In a nutshell, this ingredient is Visual State Manager support for Windows Presentation Foundation projects. As you know, Visual State Manager is built into Silverlight 2 but the WPF Toolkit gives you an early peek into the future of VSM-for-WPF.
The WPF Toolkit is a collection of WPF features and components that are being made available outside of the normal .NET Framework ship cycle. The WPF Toolkit not only allows users to get new functionality more quickly, but allows an efficient means for giving feedback to the product team.
Once you have the Blend 2 Service Pack 1 installed, here are the steps you need to follow to get to the VSM-for-WPF goodness:
Here are some VSM resources to get you going: http://blogs.msdn.com/expression/archive/2008/07/11/more-articles-on-visual-state-manager.aspx
Even though the built-in WPF controls (such as Button and CheckBox) weren’t designed with VSM in mind, the toolkit works some event interception magic that means your Visual States are applied provided they’re given the standard names such as Normal, MouseOver, Pressed, Disabled, Unchecked, Checked and so on. You can also use VSM-for-WPF to add interactivity to new custom controls you author yourself, although be aware that Blend will not read any default VisualState information out of the default template. And of course you can also add VSM interactivity to UserControls.
We hope you have fun!
PingBack from http://mstechnews.info/2008/10/blend-2-sp1-wpf-toolkit-visual-state-manager-for-wpf/
I tried doing this on 64 bit vista, the vsm doesn't appear when I reopen window1.xaml...what could I be missing? I updated the registry for 64 restarted blend and imported the dll...do I need a namespace in the xaml file?
The Blend 2 Service Pack 1 contains a secret ingredient that can be activated by installing the WPF Toolkit
I got the State panel to show up in Blend 2 SP1 but it does not appear to be interactive; that is, I cannot add a state. Do I have to add it in code behind? If so, what is the advantage of having the State panel? I am not criticizing, just trying to understand. :)
As mentioned above, this Blend support for VSM in WPF is similar to that for Silverlight. So you can only add states to a UserControl or a control template.
To clarify the above, you cannot add States to project items of type Window, Page or ResourceDictionary.
Got it! Wow, that is Awesome! I was confused because an SL project allows you to create States right on the main Workspace. Putting it into a UserControl is fine though, just a little extra work. Thanks for the help.
Now that the Visual State Manager (VSM) is part of the WPFToolKit, I thought I’d show a basic example
I’ve already blog’d about the WPF Toolkit & the WPF Ribbon Preview .  One of the things that
Some great WPF resources/previews were made available after the PDC keynote: · WPF Toolkit including
Can you change the state of a user control from an event on the parent window? How?
Der Visual State Manager für Silverlight in Expression Blend 2 (SP 1) ist zweifellos eines der Lieblingsfeatures