[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)


This document describes common page concepts, as well as features that are specific to pages of individual types only.

Expanded Page Area

Before you start learning about page types and features, take a look at what a page is and what area it occupies. At runtime, end-users cycle through wizard windows, which are not the same as wizard pages. A window consists of a wizard page, plus a bottom area where navigation buttons sit (see the figure below).

Although navigation buttons are certainly related to the currently displayed page, technically they belong to the wizard itself, and their parent region can be customized by using the Wizard.FooterTemplate property. To learn more about navigation buttons, refer to this article.

Expanded Populating Wizard

To populate a Wizard with pages, add them between start and end Wizard tags at XAML mark-up, or modify the Items collection in code (see below).

At design time you can click the ellipsis button next to the Wizard's Items property in Visual Studio's property grid. This will invoke the Collection Editor dialog that allows you to add, modify, re-arrange or remove pages.

For MVVM-based applications use the ItemSource property to populate the Wizard from an external object that stores Wizard pages.

Expanded Page Types

The wizard provides three types of pages – a welcome page, regular page and completion page. These are objects of the WelcomeWizardPage, WizardPage and CompletionWizardPage classes respectively. The WizardPage class serves as a base class for welcome and completion pages.

The figure below illustrates the three regions that every page consists of – the header, side content and main page content regions.

  • Header Region. Displays the page title (a text string assigned to the WizardPage.Title property) and header (an object assigned to the Header property). To apply a custom template for this region, use the HeaderTemplate and HeaderTemplateSelector properties of the current page.
  • Side Content Region. A rectangular area docked to the page's left. Displays content assigned to the page's WizardPage.SideContent property. This region is templated by using the WizardPage.SideContentTemplate and WizardPage.SideContentTemplateSelector properties. By default, only welcome and completion pages display their side contents. To enable this area for a regular page, set the page WizardPage.ShowSideContent property to true.
  • Content Region. A central page area that displays main page content. The ContentTemplate and ContentTemplateSelector properties specify a template applied to this region.

Pages of different types diverge in default Show... property values (there are four boolean Show... properties that specify whether the related navigation button should be displayed). This causes a Wizard to display different navigation buttons for different pages.

  • Next and Cancel buttons for welcome pages
  • Next, Cancel and Back buttons for regular pages
  • Back, Cancel and Finish for completion pages

Apart from side content region visibility and navigation button presets, pages of all three types are identical. It is also important to note that the wizard does not require a strict welcome-regular-completion page order. You can create any page sequence you want.

Expanded See Also

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