How to: Register Customized Messaging Rules Clients

Article
08/29/2006

Customized messaging rules clients require two separate registry entries. The first one registers the messaging rules client as a COM server, specifying its GUID. The second entry specifies the message transport(s) to use.

Note For information on how to work with the Windows CE registry, see Registry Fundamentals in the Windows CE documentation.

To register the customized messaging rules client as a COM server

Create and save 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]
    = REG_SZ: The name of the messaging rules client DLL.

Example

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

[HKEY_CLASSES_ROOT\CLSID\{28A42C00-1255-4dc7-9E0A-FA2F77EFB694}\InProcServer32]
    = "FromSusan.dll"

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 tranport that the messages to be processed arrive upon. Replace the <CLSID> key entry with the messaging rules client's class identifier (CLSID).

[HKEY_LOCAL_MACHINE\Software\Microsoft\Inbox\Svc\<TransportName>\Rules]
    <CLSID> = dword: 1

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

Example

The following example demonstrates how to register a custom messaging rules client that moves incoming SMS messages from the Inbox folder to a specified folder.

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

How to: Register Customized Messaging Rules Clients

Example

Example

See Also

Additional resources