Just my 2 cents.
1. Try to use master pages. You are going to love them. I have couple
internal rules for myself for any .NET project that I start and one of them
is "Always create and use MasterPage" even if it's empty...
2. Design when there is only one default.aspx page is workable. I actually
have developed E-commerce projects which has only on default.aspx (it's
completely functional and working, about 3 thousand visitors a day).
The only problem with this approach is that people love to have different
URLs. They like ability to add them to "My Favorites" or send a link to
their buddies in email...
So one page approach presents some challenges and usually needs a URL
rewriting.
Here is my site:
http://www.mspiercing.com try to hit it. You will never
tell that in reality there is only one default.aspx page there.
But from my experience, unless you are developing "framework" like
DotNetNuke, the single page design is not worth all problems it creates in
most projects.
I do believe in nice structurization though. So forum aspx pages reside in
"forum" folder, picture gallery in "gallery" folder....
George.
<ol*******@goog lemail.comwrote in message
news:53******** *************** ***********@d4g 2000prg.googleg roups.com...
>
I'm an experienced web developer - but haven't used master pages much.
I find that I'm not really comfortable with them - so perhaps I'm
missing something.....
When I first read about them I was shocked that the content
placeholder pages need knowledge of which master page they were in -
I'm happier now I understand they can be set dynamically - but I still
can't help thinking that they provide nothing on top of a reasonable
page/usercontrol design ....
...in fact I prefer a design where there's only ever *one* aspx page
per site - and everything else is written as UserControls (probably
loaded dynamically with LoadControl)... this gives nice
componentisatio n and ultimate flexibility.
I tend to work in Enterprise environments.
...I'd appreciate any comments on this.
thanks,
O.