Rolling My Own ASP.NET Registration Wizard

Answer 1

This isn't really a question that I can tell.

It looks like a decent approach to me if thats what you are asking. Is there a specific problem you are having with it?

Answer 2

The wizard control is based on the MultiView control, which basically provides a means of showing one (and only one) view at a time. The only difference is that you are required to control navigation manually with the MultiView, therefore allowing you non-linear progression through the steps.

With the MultiView, the values of all controls in all the views will be stored in the ViewState, so there is no need to store them in the Session. Buttons within each view can post back, and based on the values of other controls, you can show a specific view.

Check out the ASP.NET Quickstart on MultiView and View controls

Answer 3

I'm just worried. I'm approaching phase three of this project and I want to make sure I have a solid foundation in place, before I really start building on top of it. If anyone sees any issues w/ the approach I'm taking or if they know of a better method to building dynamic registration processes, I'd be interested in their feedback.