design question, how to implement controls

[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?

[Eliyahu Goldin]

I would go for 3 pages. It is much easier, even if you need to repeat
similar components 3 times.

Eliyahu

"Davids" <db****@simnet.is> wrote in message
news:cq**********@news.simnet.is...

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?

[Davids]

well that isn't much in the spirit of .Net of reusing code blocks etc??? Is
there any application code example out there that I can learn from?

"Eliyahu Goldin" <re*************@monarchmed.com> wrote in message
news:u9**************@TK2MSFTNGP12.phx.gbl...

I would go for 3 pages. It is much easier, even if you need to repeat
similar components 3 times.

Eliyahu

"Davids" <db****@simnet.is> wrote in message
news:cq**********@news.simnet.is...

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?

[Eliyahu Goldin]

If you are taking about code-behind classes. nothing stops you from using
the same classes in 3 places. Page layout and service controls are more
difficult to reuse. In ASP.NET 2.0 there are master pages. In ASP.NET 1.1
you can make custom controls, but I wouldn't bother for just 3 pages. To
make more-or-less non-trivial control is a hassle and you have to learn a
lot of things.

Eliyahu

"Davids" <db****@simnet.is> wrote in message
news:cq**********@news.simnet.is...

well that isn't much in the spirit of .Net of reusing code blocks etc??? Is there any application code example out there that I can learn from?

"Eliyahu Goldin" <re*************@monarchmed.com> wrote in message
news:u9**************@TK2MSFTNGP12.phx.gbl...

I would go for 3 pages. It is much easier, even if you need to repeat
similar components 3 times.

Eliyahu

"Davids" <db****@simnet.is> wrote in message
news:cq**********@news.simnet.is...

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?