The System.Runtime.Caching namespace contains types that let you implement caching in NET Framework applications.
Provides a base class that represents a ChangeMonitor type that can be implemented in order to monitor changes to cache entries.
Provides information about a cache entry that was removed from the cache.
Provides information about a cache entry that will be removed from the cache.
Represents an individual cache entry in the cache.
Represents a set of eviction and expiration details for a specific cache entry.
Provides a base class for a derived custom type that monitors changes in the state of the data which a cache item depends on.
Represents an object that monitors changes to files.
Monitors directories and file paths and notifies the cache of changes to the monitored items. This class cannot be inherited.
Represents the type that implements an in-memory cache.
Represents an object cache and provides the base methods and properties for accessing the object cache.
Provides change monitoring for SQL Server databases. This class cannot be inherited.
Specifies the reason why a cache entry was removed or an entry is about to be removed.
Specifies a priority setting that is used to decide whether to evict a cache entry.
Represents a set of features that a cache implementation provides.
Defines a reference to a method that is called after a cache entry is removed from the cache.
Defines a reference to a method that is invoked when a cache entry is about to be removed from the cache.
Defines a reference to a method that handles changes to monitored items.
The classes in this namespace provide a way to use caching facilities like those in ASP.NET, but without a dependency on the
The output caching functionality and types in the System.Runtime.Caching namespace were introduced in .NET Framework 4.
The caching types that are provided in this namespace offer the following features:
Caching is accessible to all .NET Framework applications (not just ASP.NET).
Caching is extensible.
You can create custom caching providers. For example, instead of using the default in-memory cache engine, you can create custom providers that store cache data in databases, in custom objects, or in the file system.