[Expand]General Information
[Expand]WinForms Controls
[Expand]ASP.NET Controls and MVC Extensions
[Expand]ASP.NET Bootstrap Controls
[Expand]ASP.NET Core Bootstrap Controls
[Collapse]WPF Controls
 [Expand]What's Installed
 [Expand].NET Core 3 Support
 [Expand]Common Concepts
 [Expand]MVVM Framework
 [Collapse]Controls and Libraries
  [Expand]Data Grid
  [Expand]Ribbon, Bars and Menu
  [Expand]Charts Suite
  [Expand]Pivot Grid
  [Expand]Rich Text Editor
  [Expand]Tree List
  [Expand]Gauge Controls
  [Expand]Map Control
  [Expand]Layout Management
  [Expand]Windows Modern UI
  [Expand]Data Editors
  [Collapse]Navigation Controls
   [Expand]Accordion Control
   [Expand]Breadcrumb Control
   [Expand]Navigation Bar
    Office Navigation Bar
    TileNav Pane
    Tile Bar
   [Collapse]Wizard Control
  [Expand]Spell Checker
  [Expand]Property Grid
  [Expand]PDF Viewer
  [Expand]TreeMap Control
  [Expand]Gantt Control
  [Expand]Diagram Control
  [Expand]Windows and Utility Controls
   Dialogs, Notifications and Panels
  [Expand]Scheduler (legacy)
 [Expand]Scaffolding Wizard
  Redistribution and Deployment
  Get More Help
 [Expand]API Reference
[Expand]Xamarin Controls
[Expand]Windows 10 App Controls
[Expand]Office File API
[Expand]Report and Dashboard Server
[Expand]eXpressApp Framework
[Expand]eXpress Persistent Objects
[Expand]CodeRush Classic
[Expand]Cross-Platform Core Libraries
[Expand]Tools and Utilities
 End-User Documentation
View this topic on docs.devexpress.com (Learn more)


End-users navigate through wizard windows by clicking navigation buttons. The DevExpress Wizard control provides four embedded navigation buttons - Next, Back, Finish and Cancel. These buttons are located in a separate footer region below the page area (see the figure below).

Navigation buttons belong to the wizard footer region, which is separate from pages. However, each individual page provides four boolean Show... properties (e.g., WizardPage.ShowFinish). Using these properties you can display different button sets for different pages. The following mark-up illustrates an example.

Pages of welcome, regular and completion types have their own default button presets. For instance, if a regular page in an XAML sample above had no explicitly specified buttons, it would have displayed a default set of Next, Back and Cancel buttons.

In case your page content already contains buttons that you intend to use for navigation, you can completely hide the entire footer region with its default buttons by setting the WizardPage.ShowFooter property to false.

Expanded Button Availability

Wizard navigation buttons support enabled and disabled states. To display a button as disabled, set the related Allow... property to false (e.g., the WizardPage.AllowFinish property for a Finish button). This feature can be used to prompt an end-user to perform a specific action. For instance, the following figure illustrates a regular wizard page that displays long text and a check box. The 'Next' button is disabled unless users tick the check box.

In this case, you can bind the WizardPage.AllowNext property to a CanGoNext property from code-behind.

A check box in its turn is bound to the IsAgreed property.

Then, you can easily synchronize these properties, so that the check box will affect the page WizardPage.AllowNext property.


Refer to the MVVM Framework documentation to learn more about property bindings and update notifications.

Expanded Custom Buttons

Using the Wizard.FooterTemplate property, you can manually template the footer region. This includes implementing your own buttons with custom content and behavior. In order to assign default navigation behavior to these buttons, use attached IsButton... properties. Note that each button can still have its Click event handler and thus can perform both navigation and your own custom action. The following XAML mark-up illustrates an example.

The result is shown below.

Expanded See Also

Is this topic helpful?​​​​​​​