Registering Customized Messaging Rules Clients

4/8/2010

Customized messaging rules clients require two separate registry entries.

• The first entry registers the messaging rules client as a COM server, specifying its GUID.
• The second entry specifies the message transport(s) to use.

To register the customized messaging rules client as a COM server

• Create a new registry key with the following registry key structure. In the key, replace {GUID} with the messaging rules client's Globally Unique Identifier (GUID).

  [HKEY_CLASSES_ROOT\CLSID\{GUID}\InProcServer32]
      "Default" = REG_SZ: "MyMS.dll"     // The DLL that implements the Messaging Rules Client.
  

To register the list of supported messaging transports

• Create and save a new registry key with the following registry key structure. In the key, replace <TransportName> with the name of the message transport used for these messages. Replace the <CLSID> key name with the class identifier (CLSID) for the Messaging Rules Client.

  [HKEY_LOCAL_MACHINE\Software\Microsoft\Inbox\Svc\<TransportName>\Rules]
      <CLSID> = RG_DWORD: 0x000001
  

  Note

  Currently, SMS is the only supported value for <TransportName>.

Example

The following code example demonstrates how to register a custom messaging rules client with a DLL named "SMSChess.dll".

[HKEY_CLASSES_ROOT\CLSID\{28A42C00-1255-4dc7-9E0A-FA2F77EFB694}\InProcServer32]   // Be sure to include the braces in the GUID entry.
    = "SMSChess.dll"

The following code example demonstrates how to register the message transport(s).

[HKEY_LOCAL_MACHINE\Software\Microsoft\Inbox\Svc\SMS\Rules]
    "{28A42C00-1255-4dc7-9E0A-FA2F77EFB694}" = 0x000001

See Also

Tasks

Registering Customized Messaging Transports
Registering Customized Messaging Forms

Concepts

Messaging Samples
Messaging Forms

Other Resources

Messaging Common Tasks
Messaging Application Development
Messaging