Well, I would do this in one of two ways.

1. Use the core Wizard Framework (see Admin/Portal/Sitewizard.ascx as an example).  It uses asp:panels for each "page".

2. Create your own master control, which has 4 panels.  place one of your controls in each panel.  Control the Forward/Back behaviour by making the relevant panel visible.  As all the controls are in the control tree at all times, you should have access to relevant properties/method of any of the controls, by making them public.  In fact, you have programmatic acess to the values of all the controls that are on your User Control as well.

If you have 3.3 or 4.3, you can see this behaviour in ManageUsers.ascx.vb (the page displayed is controlled by a tabstrip across the top, but the principle is the same), which contains a User (User.ascx), Membership (Membership.ascx), Password (Password.ascx), Roles (SecurityRoles.ascx) and profile (Profile.ascx), all of which are PortalModuleBase controls.

---

Charles Nurse Chief Architect Evoq Content Team Lead, DNN Corp. Want to contribute to the Platform project? - See here

MVP (ASP.NET) and ASPInsiders Member

Sorry for the delay.

I am trying to get item 2) working.

How can I make the controls public?

ASP.NET 2/VS2005 hides the control declaration code.

I have looked at the ManageUsers.ascx page and have noticed that the main page refers to controls on other usercontrols. VS puts a blue line underneath with a message saying 'not defined' and yet the site compiles and runs.

I am trying the same thing and I get build errors. (Using 4.0.3)

Is there a build/compile flag set somewhere?

Regards

Mike