System.Web.HttpContext.Current.Cache Different Results Returned In Different Browsers
asp.net,web-services,caching,httpcontext.cache
You are setting the HttpContext object for the current request. This is why each browser is having its own cache set and you are seeing different times for each user. You can set this to httpContext.cache and set the cache to current application domain. MSDN This uses HttpRuntime.cache anyways to...
Checking for null HttpContext.Current.Cache value
HttpContext.Current could be null. HttpContext.Current.Cache[Key] could be null. If either of those are null, it would result in the error you are getting....
Understanding HttpContext.Current.Cache
I am not certain which would win out. It seems that this code is setting the slidingExpiration and the absoluteExpiration. I would assume the latter would win in this but the MSDN documentation says that you should only use one or the other. If using the slidingExpiration, you should set...
Why i have to put my object twice in HttpContext Cache before it keep it for good?
c#,asp.net,asp.net-mvc,caching,httpcontext.cache
The reason why my cached item was removed immediately after his insertion was because the AppDomain get unloaded after the first call to the website. By catching the unload event of the AppDomain, i've been able to know the shutdown reason. The antivirus was scanning a file of the website...