I’m working on an ASP.NET MVC project and I’ve come to the point where I want to start considering my caching strategy. I’ve tried to leave my framework as open as possible for the use in caching.
I need to fill some dropdown boxex from some reference data. i.e City List, Country List etc. I need to fill it in various webforms. I think, we should cache this data in our application so that, we don’t hit database on every form. I am new to caching and ASP.Net. Please suggest me how to do this.
I would like to not cache my aspx pages anywhere. For some reason IE ignores meta tags which are set from my master page
I am trying to implement a generic thread-safe Cache method, and I wonder how I should implement the lock in it.
I’m using OutputCache in my page that has a user control, but I don’t want to cache this specific user control because it’s related to a user login (if I access the page, I see the page as if I were authenticated with another user).
Can anyone explain why you cannot insert a null object into the ASP.NET cache?
I have a file which is an XML representation of some data that is taken from a Web service and cached locally within a Web Application. The idea being is that this data is very static, but just might change. So I have set it up to cache to a file, and stuck a monitor against it to check if it has been deleted. Once deleted, the file will be refreshed from its source and rebuilt.
I’m troubleshooting a caching issue on a set of secured pages and have realized that the Header needs to be modified for all Responses. As I put together a solution, I want to know the difference between HttpContext.Current.Response and Page.Response and when each object should be used in an app.
According to this question, I want to know if asp.net’s system.web.caching.cache is good for me, or I should use database caching?
I am using ASP.NET’s data caching API. For example: