Home/ Questions/Q 567667
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T13:06:27+00:00

All in WPF: Developing a wizard application, user has to answer a number of

  • 0

All in WPF:

Developing a wizard application, user has to answer a number of simple questions before brought to the main app. The main app is then prefilled with the information obtained from the wizard.

I started with a Window which I then planned to add usercontrols to. The main window would have the user control in the first row, then Next and Previous buttons to control moving between the controls in the second row. This way I could easily control the logic to switch between screens like: 

WizardControl1.IsVisible = false;
WizardControl2.IsVisible = true;

But for some reason, user controls do not have setter for IsVisible. Hurray.

So then I thought I would just use seperate windows for each section of the wizard. The problem with this approach is that now when stepping between, the window opens in random positions, and by steppign through the wizard with next, the next window pops up randomly which is really distracting and frustrating.

So how can I develop a wizard properly? I don’t get why this is so hard…not exactly rocket science… replacing text and controls and storing input after pressing next/previous!

Thanks

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I’d probably aproach this using data binding and template selectors. Have the wizard form bind to a “WizardData” class, which exposes a list of “WizardPage” base classes.

    The WizardData class can expose properties defining the correct info on the forms, and display a control for the main page that uses a template selector to determine the proper control to display based on the actual type of the particular wizard page.

    It sounds like more work than it is, really. It also gives you the benefit of good separation between code and UI (all “work” is done by the WizardData and WizardPage classes), and the ability to test logic independent of the UI.

    It’s also a very WPF/MVVM way of approaching the problem.

    • 0