Scott Hanselman's Computer Zen - "Attaching a CacheDependancy to a ASP.NET Page using Output Caching" or "I can't believe they didn't think of this...oh sweet, they did!"

First time here? Check out the site's "greatest hits" or read a post from the archives. Feel free to leave a comment or ask a question, and consider subscribing to the latest posts via RSS or e-mail. Thanks for visiting!

Do you Tweet? Follow me on Twitter @shanselman or learn how to use Twitter!

Latest Tweet:

« Undocumented configuration setting for X... | Main | Tablet PC vs. Smart Display comparison »

"Attaching a CacheDependancy to a ASP.NET Page using Output Caching" or "I can't believe they didn't think of this...oh sweet, they did!"

Posted 2003-02-19 02:21 PM in Web Services | ASP.NET.

ASP.NET caching This seems like an obvious thing to want to do, but I can't see how. I have a bunch of pages using OutputCaching, like <%@ OutputCache Duration="600" VaryByParam="none" %> but the pages use additional data points / files that I'd like to add as additional cache dependencies. I can create the extra CacheDependency objects, but can't see how to connect them up to the cache entry for the page. I can't beleive the ASP.NET guys didn't think of this.[Simon Fell]

Simon is looking to add a CacheDependancy to a ASP.NET Page using Output Caching, he'll need to use HttpResponse.AddCacheItemDependency and HttpResponse.AddCacheItemDependencies.

The most interesting thing about what Simon says is "I can't believe the ASP.NET guys didn't think of this." That's funny, because I know as well as anyone that the Microsoft guys aren't perfect, but when it comes to the .NET Framework, I'll tend to search just a little harder on the faith that what I need HAS to be there...because they must have thought about this. As you spend time with the .NET Framework you'll increasingly get that same attitude; they really did think this thing through.

Thursday, February 20, 2003 12:55:16 AM (Pacific Standard Time, UTC-08:00)

I think Simon's doubt was that you can declaratively set the cache to key off params, but not declaratively set things like file dependencies. I don't think he thought this through, however, since that could become a nightmare in some deployment scenarios.

John St. Clair

Monday, October 10, 2005 11:48:48 PM (Pacific Standard Time, UTC-08:00)

It all depends how you read "I can't beleive the ASP.NET guys didn't think of this". He may have being saying it in a ".NET is so good that there must be a way to do this..." rather than a "I hate M$" vent :)

Josh

Comments are closed.