Tuesday, 15 February 2011

c# - What is happening with html file with asp @page directive and content tags within it -



c# - What is happening with html file with asp @page directive and content tags within it -

with asp.net familiar creating master page , beingness able set master page .aspx file.

with 1 of our sites work given ftp access edit static html pages. within these html pages few asp tags, page directive title, language , masterpagefile attributes, , few content tags id, contentplaceholderid , runat attributes.

my question how doing this? if add together master page in visual studio own project unable pick master page .html files. somehow building/overwriting .aspx file after upload? if go website url show .html extension.

within these html pages few asp tags, page directive title, language , masterpagefile attributes, , few content tags id, contentplaceholderid , runat attributes.

then host processing these .html files through asp.net runtime before serving them. @ technical level asp.net pages don't need have .aspx file extension, that's convention. web server can configured process files asp.net pages.

if through configuration of iis illustration (and specifics of vary wildly iis versions), might find (and may quite dated, haven't had under hood in iis years) mapping .aspx files aspnet_isapi.dll. same configuration can changed map .html files aspnet_isapi.dll, process them same way.

this isn't mutual practice not because of convention because server-side processing adds overhead , less performant serving static file straight web server. since .html files traditionally have static content, it's lot faster allow iis serve them straight process them through asp.net engine. it's possible, , host in question seems doing that, it's uncommon these reasons.

c# asp.net master-pages

No comments:

Post a Comment