Contains types that let you implement caching in .NET applications.
Classes CacheEntryChangeMonitorProvides a base class that represents a ChangeMonitor type that can be implemented in order to monitor changes to cache entries.
CacheEntryRemovedArgumentsProvides information about a cache entry that was removed from the cache.
CacheEntryUpdateArgumentsProvides information about a cache entry that will be removed from the cache.
CacheItemRepresents an individual cache entry in the cache.
CacheItemPolicyRepresents a set of eviction and expiration details for a specific cache entry.
ChangeMonitorProvides a base class for a derived custom type that monitors changes in the state of the data that a cache item depends on.
FileChangeMonitorRepresents an object that monitors changes to files.
HostFileChangeMonitorMonitors directories and file paths and notifies the cache of changes to the monitored items. This class cannot be inherited.
MemoryCacheRepresents the type that implements an in-memory cache.
ObjectCacheRepresents an object cache and provides the base methods and properties for accessing the object cache.
SqlChangeMonitorProvides change monitoring for SQL Server databases. This class cannot be inherited.
Enums Delegates CacheEntryRemovedCallbackDefines a reference to a method that is called after a cache entry is removed from the cache.
CacheEntryUpdateCallbackDefines a reference to a method that is invoked when a cache entry is about to be removed from the cache.
OnChangedCallbackDefines 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 System.Web
assembly.
Note
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 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.
Collaborate with us on GitHub
The source for this content can be found on GitHub, where you can also create and review issues and pull requests. For more information, see our contributor guide. In this articleWas this page helpful?
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4