[This is preliminary documentation and subject to change.]
The CostInitialize action starts the internal installation costing process. The CostInitialize action is also responsible for loading the Component and Feature tables into memory.
None
Typically, after the CostInitialize action is called, the FileCost action is called. Next, the CostFinalize action is called, which finalizes all the cost calculations and makes them available via the Component table.
Costing is the process in which the installer determines the disk space requirements for all the components comprising an installation, taking into account factors such as whether or not existing files need to be overwritten. For more information on the costing process in the installer, see Costing Standard Actions.