Is the approach for implementing substitution caching in MVC 3 contained in this page still valid? It was written in 2008 and MVC has changed dramatically since then so I’m not sure if there’s a more current implementation of this.
Obviously the concept of a view code-behind isn’t used anymore, but I’m referring more to the specifics of implementing the caching substitution itself.
The principle for substitution caching will be still same in MVC3, but MVC3 RC is adding support for the partial caching (exactly opposite way than substitution, but it can solve your issue)