Any good ideas for remembering settings on previous .ascx controls? - Extend It! ( Programming in VS2005 & 2008, ASP.Net 2.0 )

Forum General DotNetN... Extend It! ( Pr... Any good ideas for remembering settings on previous .ascx controls?

7/7/2006 9:21 AM

	Mike Grace
206 posts
www.computastat-group.co.uk

Any good ideas for remembering settings on previous .ascx controls?

Hi,

I am developing a module which has 4 view screens and a 5th edit screen.

Each one loads the next in a manner similar to a wizard and each one has a grid.

I want to have "Back"/ cancel buttons buttons on each page so that when the previous control loads, I can reinstate which row was selected and what page the grid was previously on similar to the browsers back button but "live" e.g. if I edit a record at the last stage then when I click on my button it will reload the previous page and refresh the grid.

The browsers back button only restores a cached page.

I know I can put all these settings in the URL or Session vars but I am wondering if there is an easier way or whether DNN has facilities for this.

Also, how do other people deal with this issue?

Regards

Mike

7/7/2006 9:42 AM

	Charles Nurse
2915 posts

Re: Any good ideas for remembering settings on previous .ascx controls?

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 DotNetNuke Trustee, Senior Architect, DotNetNuke Coporation	MVP (ASP.NET) and ASPInsiders Member
See my Blog for Articles on .NET, DNN and Module Development

7/10/2006 2:19 AM

	Mike Grace
206 posts
www.computastat-group.co.uk

Re: Any good ideas for remembering settings on previous .ascx controls?

Thanks,

I will try each of those ways and see which one suits me best.

It's easy when you know how!

Mike

7/18/2006 7:38 AM

	Mike Grace
206 posts
www.computastat-group.co.uk

Re: Any good ideas for remembering settings on previous .ascx controls?

Modified By Mike Grace on 7/18/2006 9:39:15 AM)

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

Page 1 of 1

Forum

General DotNetN...

Extend It! ( Pr...

Any good ideas for remembering settings on previous .ascx controls?