when is server recompilation done?

[VB Programmer]

For a 2003 ASP.NET site, when is recompilation of the site on the server
done? Only after the site is updated, or every time there has been a lull
in visits and someone visits it for the first time?

Thanks.

[Mark Fitzpatrick]

It happens when there's an update to the application, such as a change in
the web.config or one of the site's dlls. It also recompiles whenever the
application is loaded, which will happen when the app is recycled or the
first visit after the application has been unloaded due to inactivity.

Hope this helps,
Mark Fitzpatrick
Microsoft MVP- FrontPage

"VB Programmer" <do**@emailme.com> wrote in message
news:et**************@TK2MSFTNGP12.phx.gbl...

For a 2003 ASP.NET site, when is recompilation of the site on the server
done? Only after the site is updated, or every time there has been a lull
in visits and someone visits it for the first time?

Thanks.

[VB Programmer]

So, if there are no visits to the site for a few days, the FIRST person that
views the site is going to have to wait longer while it rejits? If so,
where can I change the "inactivity" definition?

Thanks!

"Mark Fitzpatrick" <ma******@fitzme.com> wrote in message
news:OI**************@TK2MSFTNGP09.phx.gbl...

It happens when there's an update to the application, such as a change in
the web.config or one of the site's dlls. It also recompiles whenever the
application is loaded, which will happen when the app is recycled or the
first visit after the application has been unloaded due to inactivity.

Hope this helps,
Mark Fitzpatrick
Microsoft MVP- FrontPage

"VB Programmer" <do**@emailme.com> wrote in message
news:et**************@TK2MSFTNGP12.phx.gbl...

For a 2003 ASP.NET site, when is recompilation of the site on the server
done? Only after the site is updated, or every time there has been a
lull in visits and someone visits it for the first time?

Thanks.

[Mark Fitzpatrick]

You can't change this behavior and it's not a good idea to. When an
application is loaded into IIS, it takes memory, cpu, and disk resources. By
unloading the web site after a timeout period IIS and the web server are
able to optimize performance for the web server as a whole, and it also
helps the application as well and ensures that unused application resources
are collected. The application will be unloaded after a specified timeout.
This timeout is normally 20 minutes after the last hit on the web
application. You can stretch this in IIS under the application settings, but
it is not advisable to set it for too long as it will degrade performance
overall.

Hope this helps,
Mark Fitzpatrick
Microsoft MVP - FrontPage

"VB Programmer" <do**@emailme.com> wrote in message
news:%2****************@TK2MSFTNGP14.phx.gbl...

So, if there are no visits to the site for a few days, the FIRST person
that views the site is going to have to wait longer while it rejits? If
so, where can I change the "inactivity" definition?

Thanks!

"Mark Fitzpatrick" <ma******@fitzme.com> wrote in message
news:OI**************@TK2MSFTNGP09.phx.gbl...

It happens when there's an update to the application, such as a change in
the web.config or one of the site's dlls. It also recompiles whenever the
application is loaded, which will happen when the app is recycled or the
first visit after the application has been unloaded due to inactivity.

Hope this helps,
Mark Fitzpatrick
Microsoft MVP- FrontPage

"VB Programmer" <do**@emailme.com> wrote in message
news:et**************@TK2MSFTNGP12.phx.gbl...

For a 2003 ASP.NET site, when is recompilation of the site on the server
done? Only after the site is updated, or every time there has been a
lull in visits and someone visits it for the first time?

Thanks.

[VB Programmer]

Thanks Mark.
"Mark Fitzpatrick" <ma******@fitzme.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...

You can't change this behavior and it's not a good idea to. When an
application is loaded into IIS, it takes memory, cpu, and disk resources.
By unloading the web site after a timeout period IIS and the web server
are able to optimize performance for the web server as a whole, and it
also helps the application as well and ensures that unused application
resources are collected. The application will be unloaded after a
specified timeout. This timeout is normally 20 minutes after the last hit
on the web application. You can stretch this in IIS under the application
settings, but it is not advisable to set it for too long as it will
degrade performance overall.

Hope this helps,
Mark Fitzpatrick
Microsoft MVP - FrontPage

"VB Programmer" <do**@emailme.com> wrote in message
news:%2****************@TK2MSFTNGP14.phx.gbl...

So, if there are no visits to the site for a few days, the FIRST person
that views the site is going to have to wait longer while it rejits? If
so, where can I change the "inactivity" definition?

Thanks!

"Mark Fitzpatrick" <ma******@fitzme.com> wrote in message
news:OI**************@TK2MSFTNGP09.phx.gbl...

It happens when there's an update to the application, such as a change
in the web.config or one of the site's dlls. It also recompiles whenever
the application is loaded, which will happen when the app is recycled or
the first visit after the application has been unloaded due to
inactivity.

Hope this helps,
Mark Fitzpatrick
Microsoft MVP- FrontPage

"VB Programmer" <do**@emailme.com> wrote in message
news:et**************@TK2MSFTNGP12.phx.gbl...
For a 2003 ASP.NET site, when is recompilation of the site on the
server done? Only after the site is updated, or every time there has
been a lull in visits and someone visits it for the first time?

Thanks.