Property Triggers and Data Triggers
A Trigger monitors a dependency property on the element it's attached to (usually inside Style.Triggers or ControlTemplate.Triggers) and applies its Setters only while Property equals the specified Value — for example Trigger Property="IsMouseOver" Value="True". A DataTrigger does the same job but watches an arbitrary bound value via Binding instead of a dependency property, which is what lets you change a Border's color when a bound OrderStatus string equals "Overdue", entirely from XAML with no code-behind. MultiTrigger and MultiDataTrigger extend this to require several conditions to be true simultaneously (an implicit AND) before their Setters apply.
Cricket analogy: A DataTrigger reacting to a bound OrderStatus value is like a scoreboard automatically flashing a 'New Record' graphic only when the batsman's runs value crosses a specific milestone number pulled from the live data feed.
EventTrigger and Storyboard Animation
EventTrigger differs from the other trigger types in that it doesn't watch a property value at all — it listens for a routed event (like Button.Click or UIElement.MouseEnter) and, on that event firing, begins a Storyboard animation rather than applying static Setters. Because EventTrigger actions run once per event firing and are not automatically reversed, a common pattern is pairing a 'MouseEnter' EventTrigger that animates a scale-up with a 'MouseLeave' EventTrigger that animates back down, since there's no implicit 'undo' the way property Triggers automatically un-apply their Setters when the condition becomes false.
Cricket analogy: An EventTrigger firing a fireworks animation the instant a six is hit is like a stadium's pyrotechnics system responding to a discrete event (ball crossing the boundary), not a continuous state — it fires once and doesn't auto-reverse.
VisualStateManager: The Modern Alternative
VisualStateManager (VSM) organizes a control's appearance into named VisualState objects grouped into VisualStateGroup collections (e.g. a 'CommonStates' group with Normal/MouseOver/Pressed/Disabled states), and transitions between them are driven by VisualStateManager.GoToState calls from the control's code, not by declarative property watching. Because VSM states are mutually exclusive within a group and support VisualTransition elements to control animation duration between specific state pairs, it largely superseded the EventTrigger/Storyboard pattern for interactive-state visuals in modern WPF and is the same model Silverlight and UWP standardized on, making templates easier to share conceptually across XAML platforms.
Cricket analogy: A match's official state machine — Toss, Innings1, Innings2, Result — where only one state is active at a time and transitions are explicit, mirrors VisualStateManager's mutually exclusive states within a VisualStateGroup.
<ControlTemplate TargetType="Button">
<Border x:Name="Bg" Background="{TemplateBinding Background}" CornerRadius="4">
<VisualStateManager.VisualStateGroups>
<VisualStateGroup x:Name="CommonStates">
<VisualStateGroup.Transitions>
<VisualTransition GeneratedDuration="0:0:0.15"/>
</VisualStateGroup.Transitions>
<VisualState x:Name="Normal"/>
<VisualState x:Name="MouseOver">
<Storyboard>
<ColorAnimation Storyboard.TargetName="Bg"
Storyboard.TargetProperty="(Border.Background).(SolidColorBrush.Color)"
To="#3B82F6" Duration="0"/>
</Storyboard>
</VisualState>
<VisualState x:Name="Pressed">
<Storyboard>
<ColorAnimation Storyboard.TargetName="Bg"
Storyboard.TargetProperty="(Border.Background).(SolidColorBrush.Color)"
To="#1D4ED8" Duration="0"/>
</Storyboard>
</VisualState>
</VisualStateGroup>
</VisualStateManager.VisualStateGroups>
<ContentPresenter HorizontalAlignment="Center" VerticalAlignment="Center"/>
</Border>
</ControlTemplate>DataTrigger, unlike Trigger, can bind to any expression reachable via Binding — including a converter's output — so you can drive visual states off computed logic (e.g. IsOverdue derived from a DueDate property) rather than only raw stored fields. This makes DataTrigger the workhorse for view-model-driven conditional styling in MVVM apps.
EventTrigger animations do not automatically reverse when the triggering condition ends, unlike property Trigger Setters which are cleanly un-applied once the condition becomes false. If you animate a property with an EventTrigger on MouseEnter, you must explicitly handle MouseLeave (or use FillBehavior/HoldEnd carefully) or the control can get stuck in its animated state.
- Trigger watches a dependency property; DataTrigger watches an arbitrary bound value via Binding.
- MultiTrigger/MultiDataTrigger require all listed conditions to be true simultaneously (implicit AND).
- EventTrigger responds to routed events by starting a Storyboard, and does not auto-reverse when the event condition ends.
- VisualStateManager organizes states into mutually exclusive VisualStateGroup collections, changed via GoToState.
- VisualTransition elements control the animation duration between specific state pairs in VSM.
- VSM is the modern, cross-platform-aligned (Silverlight/UWP-shared) approach superseding manual EventTrigger/Storyboard patterns for interactive states.
- DataTrigger is the primary tool for driving visuals off view-model computed properties in MVVM.
Practice what you learned
1. What does a DataTrigger watch, compared to a plain Trigger?
2. What is required for a MultiTrigger's Setters to apply?
3. What happens when the event behind an EventTrigger's animation stops occurring?
4. How are VisualStates within a single VisualStateGroup related to each other?
5. What method is typically used to explicitly change a control's active VisualState?
Was this page helpful?
You May Also Like
Control Templates
How ControlTemplate redefines a control's entire visual structure while preserving its behavior, using TemplateBinding and named parts.
Styles in WPF
How Style resources centralize and reuse property Setters across controls, including implicit styles, BasedOn inheritance, and Style-level triggers.
Data Templates
How DataTemplate lets WPF turn plain view-model objects into rich, reusable visual trees — the backbone of MVVM-driven UIs.
Related Reading
Related Study Notes in Microsoft Technologies
Browse all study notesWindows 10 / UWP Development Study Notes
.NET · 30 topics
Microsoft TechnologiesWindows Batch Scripting Study Notes
Batch · 30 topics
Microsoft TechnologiesMFC (Microsoft Foundation Classes) Study Notes
C++ · 30 topics
Microsoft TechnologiesSilverlight Study Notes
.NET · 30 topics
Microsoft TechnologiesXAML Study Notes
.NET · 30 topics
Microsoft TechnologiesMVVM Design Pattern Study Notes
.NET · 30 topics