The current state of the application cache can be viewed by enabling a cache feed handler. This can be useful for developers investigating cache related issues. Each item of the feed represents a cache item of the application cache along with related policy (expiration) and monitor (dependencies) values.

This handler is only intended for development and debugging purposes. Since the handler output may contain sensitive data, care should be taken to prevent public access. The default configuration of the handler will only allow local access while it is enabled.

Adxstudio Portals creates two types of cache entries that can be viewed using the handler. The first is the standard data/content object that one would expect to see in the cache. The second is a "cache key" item which is a cache item whose purpose is to be common cache dependency (change monitor) for the data items. These items can be identified by the "xrm:dependency" prefix in their key/label. They will also show up as change monitor entries under the relevant data cache items. Removing the cache key item from cache will result in related data items being removed as well.

Enabling the Handler

Add the following configuration elements to the web.config.

<configuration>

 <configSections>
  <section name="adxstudio.xrm" type="Adxstudio.Xrm.Configuration.CrmSection, Adxstudio.Xrm"/>
 </configSections>

 <system.webServer>
  <handlers>
   <add name="CacheFeed" verb="*" path="CacheFeed.axd" type="Adxstudio.Xrm.Web.Handlers.CacheFeedHandler, Adxstudio.Xrm"/>
  </handlers>
 </system.webServer>

 <adxstudio.xrm>
  <cacheFeed enabled="true" localOnly="true" objectCacheName="" showValues="true" traced="true"/>
 </adxstudio.xrm>

</configuration>

Since the feed is best viewed as raw XML text, it helps to disable the feed reader modes while viewing the handler on web browsers. Open the feed by browsing to the /CacheFeed.axd path of the portal application.