Export (0) Print
Expand All

How To: Register Custom Providers

This topic describes how to register custom providers for use with Windows AppFabric Hosting Services and Caching Services. Each custom provider must be registered in the Windows registry by the custom provider setup program after AppFabric setup. Register the custom provider in the following key path:

  • Key Path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppFabric\v1.0\Providers.

  • Subkey: Monitoring, or Persistence, or AppFabricCaching, depending upon the type of the provider.

A custom provider subkey must include the following values:

  • A (Default) name/data pair that includes the name of the provider configuration UI executable and the path where it is located.

  • A DisplayName name/data pair that indicates the provider name that will be added to the Provider drop-down list in the AppFabric Configuration Wizard page.

  • A Type name/data pair that includes the type name, Version, Culture, and Public Key.

noteNote
The AppFabric Configuration Wizard will not be able to launch a custom provider if the path for the provider configuration UI executable in the (Default) name/data pair has a space. You can resolve this issue by encasing the path in quotes.

Enter custom provider subkeys alongside the sub-keys for the providers that are included in an AppFabric installation by default.

  • The System.Data.SqlClient Monitoring provider in the System.Data.SqlClient subkey of the Monitoring subkey. This provider is part of .NET Framework 4. The provider is registered if Hosting Services is installed.

  • The sqlStoreProvider Persistence provider sqlStoreProvider subkey in the Persistence subkey. This provider is part of .NET Framework 4. The provider is registered if Hosting Services is installed.

  • The SQL Server AppFabric Caching Service Configuration Store Provider in the System.Data.SqlClient subkey of the AppFabricCaching subkey. This provider is part of AppFabric. The provider is installed and registered if the Caching Services, Cache Client, or Cache Administrator is installed.

For more information about how to create custom providers, see How To: Develop an Instance Store Provider, How To: Develop an Instance Query Provider, How To: Develop an Instance Control Provider, or How To: Use a Non-SQL Server Monitoring Database.

Community Additions

ADD
Show:
© 2014 Microsoft