Options for Directory Update entries

The following are optional for Directory Update entries:

Package files:

PC files that contain information on other files to be updated. See Directory Update package files syntax and format for more information. Package files are added to update entries by using the cwbUP_AddPackageFile API.

Callback DLL:

A DLL provided by the application programmer that Directory Update will call into during different stages of the update process. This allows programmers to perform application unique processing during the different stages of an update. A callback DLL is added to an update entry using the cwbUP_SetCallbackDLL API.

The different stages of update when Directory Update may call into the callback DLL are:

Pre-update:: This is when Directory Update is about to begin its processing of an update entry. The following entry point prototype must be in the callback DLL: unsigned long _declspec(dllexport) cwbUP_PreUpdateCallback();
Post-update:: This is when Directory Update has completed moving the files. The following entry point prototype must be in the callback DLL: unsigned long _declspec(dllexport) cwbUP_PostUpdateCallback();
Pre-migration:: This is when Directory Update is about to begin version-to-version migration of an update entry. Version-to-version migrations are triggered by QPTFIDX files. The following entry point prototype must be in the callback DLL: unsigned long _declspec(dllexport) cwbUP_PreMigrationCallback();
Post-migration:: This is when Directory Update has completed processing of a version-to-version migration of an update entry. The following entry point prototype must be in the callback DLL: unsigned long _declspec(dllexport) cwbUP_PostMigrationCallback();

Attributes:

Set the type or mode of the update to be performed. Combinations of the attributes are allowed. Attributes are:

File-driven update:: The files in the target directory are compared to the files in the source directory. Target files with dates older than the source files are updated. No new files will be created in the target.
Package-driven update:: The package files listed in the update entry are scanned for files to be updated. The dates of the files that are listed in the package file are compared between the source and the target directories. The source files with newer dates are updated or moved into the target directory. If a file that is listed in the package file does not exist in the target, but exists in the source, the file is created in the target directory.
Subdirectory update:: Subdirectories under the target directory are included in the update.
Onepass update:: Updates occur directly from source to target. If this is not specified, updates occur in two passes. The first pass of the update will copy the files to be updated into a temporary directory. Then the PC is restarted. On restart, the files are copied to the target directory. This is useful for locked files.
Backlevel update:: This controls if updates will occur if the source files are older than the target files.