J
John Dann
I'm reasonably comfortable with HTML and VB2005 coding but now want to
add some ASP.Net pages to a website. Learning ASP.Net and hosting it
on a suitable server are both doable, but my question is as follows:
I want to add in just a few ASP.Net pages to the new website. It will
probably turn out that the new site will be 75% passive (ie straight
HTML) content and 20-25% active (ASP.Net) pages. What I'm puzzling
over currently is how best to manage this mix of pages.
One feature that I do want is a common look between the HTML and ASP
pages and so I'd prefer an approach that used templates or master
pages or something similar.
Now I guess I could set up the whole site as ASP pages, using an ASP
master page but this strikes me potentially as overkill with a lot of
unnecessary code in the passive HTML pages which would be ASP in name
only but with no functional controls. Alternatively I could add in
HTML rather than ASP pagesto the website for the passive-only pages,
but then (?) presumably lose the ability to use a single master page
for the whole site.
Another concern (bear in mind that I've never set up an ASP site
before) is that passive pages with superfluous ASP code would be
served slower than the equivalent HTML page.
Any advice appreciated.
JGD
add some ASP.Net pages to a website. Learning ASP.Net and hosting it
on a suitable server are both doable, but my question is as follows:
I want to add in just a few ASP.Net pages to the new website. It will
probably turn out that the new site will be 75% passive (ie straight
HTML) content and 20-25% active (ASP.Net) pages. What I'm puzzling
over currently is how best to manage this mix of pages.
One feature that I do want is a common look between the HTML and ASP
pages and so I'd prefer an approach that used templates or master
pages or something similar.
Now I guess I could set up the whole site as ASP pages, using an ASP
master page but this strikes me potentially as overkill with a lot of
unnecessary code in the passive HTML pages which would be ASP in name
only but with no functional controls. Alternatively I could add in
HTML rather than ASP pagesto the website for the passive-only pages,
but then (?) presumably lose the ability to use a single master page
for the whole site.
Another concern (bear in mind that I've never set up an ASP site
before) is that passive pages with superfluous ASP code would be
served slower than the equivalent HTML page.
Any advice appreciated.
JGD