Overhead converting .htm files to .aspx

[mwhite]

Hi, I have an old .htm site that I need to protect with Forms
Authentication.
I know that I can change the filetype of all these files to .aspx, and
this lets the Forms Authentication protect them, however I saw on
msdn.microsoft.com that this incurs some additional overhead. Does
anyone know how severe the overhead will be? I cannot find any helpful
info, and the client does not wish to have the entire site redeveloped
(the alternative).
Any help gratefully received!

Mat

 

[John Timney \(MVP\)]

It causes the invocation of the ISAPI that handles asp.net pages for each
page request with that extension, each page will be compiled at first
request executed at request time. You wont know what the overhead will be
without measuring execution time against current delivery time.

Fish around for some performance testing tools to determine what the
difference will be.
http://aspnet.4guysfromrolla.com/articles/062304-1.aspx

Regards

John Timney (MVP)
http://www.johntimney.com

 

[bruce barker \(sqlwork.com\)]

iis is highly optimized to serve static content. using asp.net to serve
static the pages is probably an order of magnitude slower (if not more). but
it should make little difference unless you re a very high volume site.


-- bruce (sqlwork.com)

 

[mwhite]

Thanks, since it's only for an internal intranet, I think they will be
more than happy with a slight overhead, rather than the wait to have
the site redeveloped!

Mat