ASP.NET Application Lifetime & Cache Expiration

[Sashko]

Hi,

I made an ASP.NET (.NET 1.1) application that uses the Context.Cache
object within Global.asax as a static member. It is set up in such a
way that whenever the cache items expire, they recache themselves
automatically.

However, I ran into a problem. It seems like my application ends
prematurely (or is recycled or something), usually after the last
session is done, and I lose all my Cache saved objects. Next time the
page is viewed, all the data has to be reloaded as Application_Start is
called.

Is there a configuration setting that I can tweak that will tell IIS or
ASP.NET to keep my application alive and persist the Application Cache?

Thanks!

~Alex

 

[Joerg Jooss]

Thus wrote Sashko,

Hi,

I made an ASP.NET (.NET 1.1) application that uses the Context.Cache
object within Global.asax as a static member. It is set up in such a
way that whenever the cache items expire, they recache themselves
automatically.

However, I ran into a problem. It seems like my application ends
prematurely (or is recycled or something), usually after the last
session is done, and I lose all my Cache saved objects. Next time the
page is viewed, all the data has to be reloaded as Application_Start
is called.

Is there a configuration setting that I can tweak that will tell IIS
or ASP.NET to keep my application alive and persist the Application
Cache?

System.Web.Caching.Cache works in memory, but Enterprise Library 2.0 offers
a durable cache class with a similar API.

Cheers,