<sonicsoul@gmail.com> wrote in message
news:1148575457.471627.29860@y43g2000cwc.googlegroups.com...
> Hello,
>
> I have a question regarding the automatic restarting of asp.net web
> applications.
> If I modify a aspx file, it is my understanding that the runtime will
> generate a new assembly based on it, and place it in the temporary
> asp.net files directory aside of the old version of this assembly, and
> route new requsts to the new assembly. When maximum number of reloads (
> 15 by default ) is reached, AppDomain will be unloaded and the web app
> will be restarted..
>
> does this means that the behavior is changed from 1.1 where, when a
> page was using a code behind file, instead of assembly, I could change
> that code behind file infinitely and this would only reload the
> assembly for that page instead of restarting the whole runtime, but now
> only x amount of such changes are avaialble ?
>
> I would be interested in preventing this and any other non explicit
> application restarts by the framework. or at least knowing exactly when
> to expect them.
>

"sonic" <sonicsoul@gmail.com> wrote in message
news:1148689600.678610.200070@j73g2000cwa.googlegroups.com...
> thanks Alvin,
>
> The reason i brought this up, is that I consider it to be a great
> feature in 1.1 where if a aspx page referenced a codebehind by src
> attribute, changing the codebehind file did not mean restarting the
> worker process and therefore the whole site.
> Our production environment could not be restarted during business hours
> due to heavy load but it was nice to be able to change individual files
> at times in emergency situations during the day w/out this reprecation.
>
>
> Is there a equivalent way to address this in 2.0 ?
>