I’m storing a dataset in an ASP.Net WebApplication-Cache. Every user in this intranet-app uses the same instance. On insert/update/delete-actions the database will be updated and the dataset is modified accordingly.
Right now I have an Azure Cloud Service hosting an MVC app that – currently – when updated using the VIP swap method from Staging <> Production, kills all sessions. I haven’t done any configuration around Session management, so this is to be expected.
I know that most people recommend using HttpRuntime.Cache because it has more flexibility… etc. But what if you want the object to persist in the cache for the life of the application? Is there any big downside to using the Application[] object to cache things?
Long time listener – first time caller. I am hoping to get some advice. I have been reading about caching in .net – both with System.Web.Caching and System.Runtime.Caching. I am wondering what additional benefits I can get vs simply creating a static variable with locking. My current (simple minded) caching method is like this:
I’m trying to get YSlow to give me an A on the “Add Expires header” section by setting the web.config file.
At the moment I am working on a project admin application in C# 3.5 on ASP.net. In order to reduce hits to the database, I’m caching a lot of information using static variables. For example, a list of users is kept in memory in a static class. The class reads in all the information from the database on startup, and will update the database whenever changes are made, but it never needs to read from the datebase.
We know that IIS caches ConfigurationManager.AppSettings so it reads the disk only once until the web.config is changed. This is done for performance purposes.
I have an ASP.NET site with a fairly slow search function, and I want to improve performance by adding the results to the cache for one hour using the query as the cache-key:
While writing a custom IHttpHandler I came across a behavior that I didn’t expect concerning the HttpCachePolicy object.
Should dynamic business objects for a site be stored in the users session or use ASP.Net caching (objects such as orders, profile information etc)?