ISyncMgrSynchronize::Initialize method (mobsync.h)
Called by the synchronization manager in a registered application handler to determine whether the handler processes the synchronization event.
HRESULT Initialize( DWORD dwReserved, DWORD dwSyncMgrFlags, DWORD cbCookie, const BYTE *lpCookie );
Reserved; must be 0 (zero).
The SYNCMGRFLAG enumeration values that describe how a synchronization event is initiated.
The size of the lpCookie data, in bytes.
Type: BYTE const*
A pointer to the token that identifies an application. This token is passed when an application invokes the synchronization manager programmatically.
This method supports the standard return values E_INVALIDARG, E_UNEXPECTED, and E_OUTOFMEMORY, and the following.
||Initialization is successful.|
||Application handler does not process a synchronization event.|
If an application does not recognize the SYNCMGRFLAG event, the application should treat the event as a manual synchronization.
A registered application handler cannot display a user interface within this call unless it is the first time the initialization method is called. An application can display any one-time initialization it needs to set up items and introduce a user to an application feature. If you need to display a user interface for a different reason as part of the synchronization process, you can use the ISyncMgrSynchronize::PrepareForSync method.
The lpCookie parameter is NULL unless a handling application invokes the synchronization manager programmatically by using UpdateItems. In this scenario, the class identifier (CLSID) identifies the handling application, and the value of lpCookie is passed in by the handling application, and then passed back by the synchronization manager during synchronization for context. The lpCookie parameter is only meaningful when SYNCMGRFLAG_INVOKE is set.
|Minimum supported client||Windows 2000 Professional [desktop apps only]|
|Minimum supported server||Windows 2000 Server [desktop apps only]|