Important:
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
A version of this page is also available for
4/8/2010

This structure is used to prototype a function to pass to RegistryNotifyCallbackto call back the client when a registry value changes.

Syntax 

typedef void REGISTRYNOTIFYCALLBACK(
  HREGNOTIFY 
hNotify,
  DWORD 
dwUserData,
  const PBYTE 
pData,
  const UINT 
cbData
);

Parameters

hNotify

The valid HREGNOTIFY handle returned from RegistryNotifyCallback.

dwUserData

User data passed back to the client with the notification.

pData

A pointer to the new value for the key value, this will be set to NULL if the value was deleted.

cbData

The number of bytes to pointed to by pData, this value will be set to 0 if the value was deleted.

Remarks

A callback matching this prototype is used to notify clients that registered for notifications using RegistryNotifyCallback.

To stop notification and to close the notification handle, it is safer to use RegistryCloseNotificationfrom within the callback. However, this type of notification is transient. Resetting the device stops the notification.

All notifications happen synchronously, so it is important to not block notifications while executing this callback.

Requirements

Header regext.h
Windows Embedded CE Windows Embedded CE 6.0 and later
Windows Mobile Windows Mobile Version 5.0 and later

See Also

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.