Custom Actions

required if we need to do things that standard actions doesn't support.
-Set a directory location to install-time value
-Set a windows installer property to install-time value

Types of custom actions:
------------------
mentioend by numbers.
ex: type 35, to set a directory location.

Type-1:
--
calls an exported function in DLL.
these functions shoud have a specific signature.
C Function Signature:
UINT __stdcall MyFUnction(MSIHANDLE hModule)

These DLLs are stored in the binary table of msi file(Installation Database).


Type-2:
--
Calls an executable with command line arguments.
.exe stored in binary table


Both Type1 and 2 DLL or EXE embedded in msi-extracted at install time.THey are not installed with product.

Type 17 & 18:
----
Calls a .DLL/.EXE, which are installed with the product.
Must sequence correctly.

As files should be already installed, they should be kept after InstallFiles standard action.
Non-deferred actions should be kept after InstallFinalize.

Type 34
---
Calls .EXE using a path from a DIRECTORY table entry

Type 50
---
Calls .EXE using a path from a WIndows Installer property

Type 19
---
Displays an error message from a formatted string and terminates installation.

Type 35
--
Sets an install directory from a formatted string

Type 51
--
Sets a property from a formatted string

Type 5,6,21,22,37,38,53,54
---
Script executing custom actions


http://bit.ly/CustomActionReference