.NET Caching and App Pools

[Murdz]

Hi,

As far as .NET caching goes on IIS, if 2 .NET websites are in the same app pool can they access the same cache items (Using HttpContext.Cur rent.Cache) ? Or is this cache collection always seperate for each .NET application?

Cheers

[kenobewan]

Here is an article that may help:
IIS and ASP.NET: The Application Pool

[Murdz]

Thanks, I did read that but it didn't fully delve into what I was after. I have learnt, though, that this is not possible.

Is there a way, then, of two different projects being able to manipulate the Cache items of one another? For example, say there is a .NET website and a .NET admin section for that website. The dream is to have the 2 as seperate projects so that a deploy of the website doesn't mean a deploy of the admin, and vice versa. The problem, however, is that the admin system needs to update / remove Cache items that the website accesses... Is there any way to do this? Or must they both exist within the same project (application) in order to modify the Cache for each other?

[kenobewan]

Thanks, I did read that but it didn't fully delve into what I was after. I have learnt, though, that this is not possible.

Is there a way, then, of two different projects being able to manipulate the Cache items of one another? For example, say there is a .NET website and a .NET admin section for that website. The dream is to have the 2 as seperate projects so that a deploy of the website doesn't mean a deploy of the admin, and vice versa. The problem, however, is that the admin system needs to update / remove Cache items that the website accesses... Is there any way to do this? Or must they both exist within the same project (application) in order to modify the Cache for each other?

Easier to stick with the one project and probably more secure.

[Murdz]

Double post, see below.

[Murdz]

Cheers.

The only other option that I can really think about, aside from reading some DB value (as the whole point of caching is to avoid DB calls) is to have a CacheDependency on a file and simply update that file through the admin system; thus the cache for the website will expire.

[kenobewan]

Another way may be using a class library. If the classes or configs are shared, then you may be able to control caching across two applications. An even easier way may be to reference a client side file in both apps that does this job. Never used this approach, so just a suggestion. HTH.

[Murdz]

Interesting.

Cheers kenobewan.