Accessing many objects at once can be a high-processing task, so some sort of programmatic caching is recommended in addition to the internal caching mechanisms discussed above for templates that access many objects via the Publishing API. The preferred method of caching for MCMS is ASP.NET output caching. This will reduce the number of objects that MCMS must compile when a page is requested, therefore reducing the amount of processing required.
ASP.NET output caching is used to store content created by dynamic pages. Instead of assembling the page over and over again, the content is retrieved from the cache. There are two types of ASP.NET output caching:
Page caching
User control caching (also called ASP.NET fragment caching)
If you are using legacy ASP-based templates from MCMS 2001, you cannot utilize ASP.NET output caching. However, MCMS 2001 includes its own fragment caching feature for ASP-based templates. We will not cover this caching...