Common Web Site Header

I have a simple question that I would like some opinions on regarding common
web site headers. I have several web sites (IIS 6), spread across different
physical machines that have the same web site header. They are currently a
mix of ASP.NET 2.0, 1.1, and plain old HTML pages. For years, I have used
ASP.NET user controls for the server-side headers and external JavaScript
files to inject the common headers into the HTML files. What I would like is
a single header source for every different type of page I serve (ASP.NET and
HTML). Without migrating my HTML to ASP.NET, is external JavaScript the best
way to do this (I don’t particularly care for this method)? What kind of
performance implication would using server-side includes have? I’d just like
some opinions on what seems like a remedial subject.

Re: Common Web Site Header

=?Utf-8?B?S2l0dHlIYXdr?= wrote on 24 jan 2007 in
microsoft.public.inetserver.asp.general:

> I have a simple question that I would like some opinions on regarding
> common web site headers. I have several web sites (IIS 6), spread
> across different physical machines that have the same web site header.
> They are currently a mix of ASP.NET 2.0, 1.1, and plain old HTML
> pages. For years, I have used ASP.NET user controls for the
> server-side headers and external JavaScript files to inject the common
> headers into the HTML files. What I would like is a single header
> source for every different type of page I serve (ASP.NET and HTML).
> Without migrating my HTML to ASP.NET, is external JavaScript the best
> way to do this (I don’t particularly care for this method)? What
> kind of performance implication would using server-side includes have?
> I’d just like some opinions on what seems like a remedial subject.
>

This is a classic asp group.

Dotnet questions should be asked in


--
Evertjan.
The Netherlands.
(Please change the x'es to dots in my emailaddress)

Re: Common Web Site Header

KittyHawk wrote:
> I have a simple question that I would like some opinions on regarding
> common web site headers. I have several web sites (IIS 6), spread
> across different physical machines that have the same web site
> header. They are currently a mix of ASP.NET 2.0, 1.1, and plain old
> HTML pages. For years, I have used ASP.NET user controls for the
> server-side headers and external JavaScript files to inject the
> common headers into the HTML files. What I would like is a single
> header source for every different type of page I serve (ASP.NET and
> HTML). Without migrating my HTML to ASP.NET, is external JavaScript
> the best way to do this (I don't particularly care for this method)?
> What kind of performance implication would using server-side includes
> have? I'd just like some opinions on what seems like a remedial
> subject.

There was no way for you to know it (except maybe by browsing through
some of the previous questions before posting yours - always a
recommended practice), but this is a classic asp newsgroup. ASP.Net is
a different technology from classic ASP. While you may be lucky enough
to find a dotnet-savvy person here who can answer your question, you
can eliminate the luck factor by posting your question to a newsgroup
where the dotnet-savvy people hang out. I suggest
microsoft.public.dotnet.framework.aspnet.
There are also forums at www.asp.net where you can find a lot of people
to help you.
--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.