D
Davids
trying to stop thinking classic ASP way, I want to ask you a design question
about how to seperate page functions. Let's say I have a blog.aspx page
which has 3 subpages;
1) display all (short version) blog entries for selected month or blog
category
2) display selected blog (long version)
3) display list of blog categories and allow user to select one
the old way was to use Request.Querystring("action") where action would be
allblogs, selectedblog or blogcats. A single .asp page would handle it with
3 switch... case statements. No problem doing that in .Net either but the
problem is that all controls in the .aspx page are rendered even though only
one is being used.
So concerning these controls, should I struggle to somehow disable them
until used or do I really need to have three seperate .aspx pages for these
three different - still similiar - sections?
about how to seperate page functions. Let's say I have a blog.aspx page
which has 3 subpages;
1) display all (short version) blog entries for selected month or blog
category
2) display selected blog (long version)
3) display list of blog categories and allow user to select one
the old way was to use Request.Querystring("action") where action would be
allblogs, selectedblog or blogcats. A single .asp page would handle it with
3 switch... case statements. No problem doing that in .Net either but the
problem is that all controls in the .aspx page are rendered even though only
one is being used.
So concerning these controls, should I struggle to somehow disable them
until used or do I really need to have three seperate .aspx pages for these
three different - still similiar - sections?