Re: Disable cache for ASP>NET at global level in IIS

From: Charles Smith (advdata_no_s_pa_m_at_cox.net)
Date: 03/03/05 

Date: Wed, 02 Mar 2005 18:46:38 -0700

On 1 Mar 2005 06:57:43 -0800, "Jeremy Smith" <godtoall@hotmail.com>
wrote:

>
>Rany,
>Thanks for the responce.
>I should have added earlier that I already set this setting. It looks
>like something in ASP.NET module for caching. I noticed that the
>Developer has a 2 hr setting and after 2 hours the webiste reponce is
>updated. So I know it has to be in ASP.NET setting. Might need to
>submit this question to a different group. thanks

First ASPX files are compiled on first use to a dll and cached (the
code behind is precompiled). I doubt the "don't cache asp pages"
setting will change this behavior.

Second you might be running into an important feature designed for
deploying production changes. ASP.Net allows you to deploy a new
version of the application right on top of the old one while it is in
use! Remember the web is really stateless. Changing the application
files in the middle of an ASPX application session would be fatal.
What ASP.net does to save your *** is use the old files from the
cache for the current sessions. If I remember right a new session will
use the new files right along side the old sessions. If you have a
session open in an external browser you will get the old files after a
recompile in the IDE. Make sure the developers are using the IDE's
browser or closing the external browser window between compile cycles
so that they will open a new session.