ASP.NET

When looking to speed up content that will be served from an ASP.NET MVC controller, one of the options I evaluate is the built in Output caching mechanism. Output caching is great because it’s easy to setup, easy to maintain and it can give a big improvement for a small amount of code. Sometimes, the cached item will need to be flushed (and regenerated / recached). The built in mechanisms for handling this – using cache expiration, or varying the cached output by one of many parameters – handle most use cases pretty easily....

I recently switched jobs (and switched states) and used several approaches that I haven’t heard used anywhere else, so I wanted to share what worked and what didn’t work. ...