Export (0) Print
Expand All

C

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

cabinet file

Single file, usually with a .cab extension, that stores compressed files in a file library. The cabinet format is an efficient way to package multiple files because compression is performed across file boundaries, significantly improving compression ratio. For information about creating cabinets, see Cabinet Files.

checksum

Computed value that depends on the contents of a file. It is stored with data to detect file corruption. The system checks this value to ensure that the data is uncorrupted.

component

Smallest piece of an installation handled by the installer, also a building-block of an application or feature from the programmer's perspective. Examples of components are a group of related files, a COM object, or a library. For more information, see Components and Features.

committing databases

Accumulated changes made in a database. The changes are not reflected in the actual database until the database is committed. For more information, see Committing Databases.

ControlEvent

Aspect of functionality of the installer's user interface. A typical ControlEvent triggers some action by the installer upon the activation of a dialog box control or other event. For more information, see ControlEvent Overview.

costing

Method used by the installer to determine disk space requirements for installation. Costing takes into account factors such as whether existing files need to be overwritten. For more information, see File Costing.

.cub file

Validation module that stores and provides access to ICE custom actions. For more information, see Sample .cub File. For more information, see also Windows Installer File Extensions.

custom action

Written by the author of the package but not built into the installer as a standard action. For more information, see Custom Actions.

 

 

Community Additions

ADD
Show:
© 2014 Microsoft