Limitations of CAB

Nov 23, 2009 at 12:38 PM

Hi,

We are developing some projects in our company. We have gone through an extensive R&D that how Microsoft Enterprise Library can help us in our development. During our evaluation, we came to the conclusion that using Caching Application Block for caching has some serious drawbacks. Particularly due to its standalone nature, no scalability and reliability. We have also found some important readings on internet which talk about the <a href="http://www.alachisoft.com/ncache/caching-application-block_index.html">limitations of Regular Microsoft Enterprise Library Caching Application Block</a>. So anybody who is using Enterprise Library or planning to use it must also keep in mind its limitation as well.

Coordinator
Nov 23, 2009 at 8:18 PM

Hi Wes,

For ASP.NET development it is now generally recomended to use the built-in ASP.NET Caching feature, however, for Windows Forms (Smart Client) development the CAB is still "good to go". I have used it quite reliably for local caching (i.e. each user has their own cache using local memory or a DB etc).

Cheers...   Steve