visible controls?

  • Thread starter Thread starter SteveS
  • Start date Start date
S

SteveS

Hello all. I have an "update" page where a user can update any one of 10
sections (i.e., their personal login info, address info, phone number info,
preference info, etc...) Currently, I have each of the 10 sections in its
own separate panel on the .aspx. page. Initially I have them set to
Visible=false so they don't display. A panel is set to Visible only if
that is the section they are updating. Given this scenario, I have about
120 controls of text boxes, dropdown lists, and checkboxes. The reason
that I kept everything to one page is that I also do some other processing
that is common to all sections. If I had 10 different pages, then the code
would be duplicated.

I'm now finished with the page and was thinking I shouldn't have done it
this way because the .aspx page is huge, and the code-behind has several
Select Cases... needed to pick the correct panel. I would like your opinion
of the best way to handle this scenario?

I read that that performance of the a web page degrades with the more
controls that are populated. Do you think I created the page the most
efficiently? I figure I have 3 options:

1) The way I already did it - One big page with 10 different panels.
2) Have each panel as it's own separate user control for each section. Only
the control with the appropriate information is visible to the user. (If a
user control is set to visible=false, are the controls in the user control
still instantiated?)
3) Have 10 totally different pages.

I'm curious to here all your opinions!

Thank you in advance,

Steve
 
you could of done 10 pages that inhert from the same base page and therefore
avoid duplicatcation the code. the pages would have been simpler, and it
would be easier to add new sections.

-- bruce (sqlwork.com)
 
In addition to Bruce's fine suggestion, you also could have made each of
your panels into user controls.
Then you could have one page where your common code is, and it would load
each control in sequence dynamically as needed. This technique avoids
loading all 120 controls into memory at once when you're only really using a
fraction of them at any one time.
 
Back
Top