The FileCostaction initiates dynamic costingof standard installation actions.

ActionData Messages

There are no ActionData messages.

Sequence Restrictions

Any standard or custom actions that affect costing should sequenced before the CostInitialize action. Call the FileCost action immediately following the CostInitialize action. Then call the CostFinalize action following the CostInitialize action to make all final cost calculations available to the installer through the Component table.

The CostInitialize action must be executed before the FileCost action. The installer then determines the disk-space cost of every file in the File table, on a per-component basis (See Component Table), taking both volume clustering and the presence of existing files that may need to be overwritten into account. All actions that consume or release disk space are also considered. If an existing file is found, a file version check is performed to determine whether the new file actually needs to be installed or not. If the existing file is of an equal or greater version number, the existing file is not overwritten and no disk-space cost is incurred. In all cases, the installer uses the results of version number checking to set the installation state of each file.

The FileCost action initializes cost calculation with theinstaller. Actual dynamic costing does not occur until the CostFinalize action is executed.

See Also

File Costing

Send comments about this topic to Microsoft

Build date: 6/25/2009