Programmatic Client Configuration (Windows Server AppFabric Caching)

With Windows Server AppFabric, you can specify the cache client configuration settings programmatically or with an XML configuration file. The programmatic approach is an excellent choice when you want to change settings programmatically or when you do not want an XML-based application configuration file. Then, if you make any changes to your cache client configuration, you may have to recompile the application. Changes to settings in an XML-based application configuration file do not require any recompilation. For more information about XML-based cache client configuration, see XML-Based Client Configuration (Windows Server AppFabric Caching).

If you are using an XML application configuration file for client configuration with most of your application, you can override those settings programmatically.

Configuration Classes and Methods

All of the cache client configuration properties are set in an instance of the DataCacheFactoryConfiguration object. This object is passed to the DataCacheFactory constructor. For an overview of these classes and other classes involved in configuring the cache client, see Configuration Methods (Windows Server AppFabric Caching).


For a detailed description of the process and a code example, see Get Started with a Windows Server AppFabric Cache Client.

See Also


Get Started with a Windows Server AppFabric Cache Client
Enable Windows Server AppFabric Local Cache
XML-Based Client Configuration (Windows Server AppFabric Caching)
Cluster Configuration Storage Options (Windows Server AppFabric Caching)
Troubleshooting Windows Server AppFabric Caching
Using Windows PowerShell to Manage Windows Server AppFabric Caching Features
Configuration Settings (Windows Server AppFabric Caching)
Developing a Cache Client (Windows Server AppFabric Caching)
Windows Server AppFabric Caching Concepts