Dynamic Compilation is for .aspx page, and as well for Web
Services(.asmx), Web Controls(.ascx), HTTP handlers(.ashx) and global.asax.
Invoking
a Page:
Code Behind of the Page is paresed into a class that is compiled into an
assembly placed into ASP.Net – Specific Temporary Directory.
Resource mapping is stored in IIS metabase and is updated on
installation of .Net Framework to point to aspnet_isapi.dll as well.
IIS Application Mappings for
aspnet_isapi.dll
.asax(so that can’t be access from outside), .ascx, .ashx, .asmx, .aspx,
and .axd (trace.axd).
IIS 5.0
Process Model:
ISAPI extension and worker process communicate through Named Pipes.
A single copy of worker process runs all the time or configure in
<processModel> attribute to run one process per CPU in single machine is
known as web garden.
IIS 6.0
Process Model:
To use IIS 5.0 Process Model on IIS 6.0 specify the following: (although
not recommended)
In
IIS 6.0 most of the contents of <processModel> are ignored and should be
configured from directly IIS.
Applied
attributes are: autoConfig, maxIoThreads,
maxWorkerThreads, minIoThreads, minWorkerThreads, requestQueueLimit,
responseDeadlockInterval
Rest of the attributes are
ignored under IIS 6.0.
