Expression Blend and Design

The team blog of the Expression Blend and Design products.

Blend 2 SP1 + WPF Toolkit = Visual State Manager for WPF

Blend 2 SP1 + WPF Toolkit = Visual State Manager for WPF

  • Comments 20

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:

  1. Install the WPF Toolkit from http://www.codeplex.com/wpf/Release/ProjectReleases.aspx?ReleaseId=15598
     
  2. Create the following registry value and make it non-zero. The value should be of type DWORD. Or run the appropriate .REG file attached to this post (or by clicking here).
     
    • 32 bit OS : HKLM/Software/Microsoft/Expression/Blend/EnableVSM
       
    • 64 bit OS : HKLM/Software/Wow6432Node/Microsoft/Expression/Blend/EnableVSM
       
  3. If Blend was running during the previous step then restart it.
     
  4. Create a new WPF project.
     
  5. Add %Program Files%\WPF\WPF Toolkit\...\WPFToolkit.dll to the References folder (Right-click the References node in Project, then click Add Reference…).
     
  6. Close and reopen Window1.xaml. The States pane will now appear for the project.

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!

-Steve

Attachment: VSM Reg Files.zip
Leave a Comment
  • Please add 6 and 7 and type the answer here:
  • Post
  • Blend 2 SP1 + WPF Toolkit = Visual State Manager for WPF En une équation comme le rappelle l’équipe produit

  • States disappear from the State view in the design view. They are still in the XAML and all work fine, but they just do not show up in the state viewer anymore and therefore I am unable to add or change states.

    Anybody experiencing the same problem?

  • I love the VSM for WPF, it is a great feature!  I am curious, though: I can't seem to be able to use a local resource in my States.  whenever I use a local resource, say to change a Border color in MousePressed, it alters the entire template.  If I use a normal color, all is well.

    Also, is there a way to copy a state?  For instance, MouseOver has a a particular design which is different than Normal: but when I want a different design for MousePressed, I want the MouseOver state to be the starting point, not Normal.  In other words, I have to replicate the MouseOver state first, and then make my changes, in order to achieve the effect I want from MousePressed.  I hope I expressed that OK.

    Thanks for all the great work, I look forward to your future releases!

  • Hello Steve,

      Hate to beat a dead horse, but this is not working for me.  I have a full license copy of Expression Blend with SP1 and the latest WPFTookKit.  Even though I open a UserControl the States does not show up.  Not even when I modify the template for that user control either.  Any ideas?

  • Hi Rashad, if you install the October 2008 version of the WPF toolkit, set the reg key, restart Blend, create a new WPF project, reference the toolkit dll, close and reopen Window 1, then you'll get the States pane. Hope that helps.

    I would urge you to look at the Blend 3 preview though:

    http://expression.microsoft.com/en-us/cc507094.aspx#blend3preview

    -Steve

Page 2 of 2 (20 items) 12