Written by D. G. Schneider ContactEZ.net


MSI Installer Script Automation Overview

You can create MSI tables on the fly and automatically import them in the MSI, then create the DDF files that will in their turn create the CAB files. Some custom tools can for example import REG files into the Registry Table.
To create the CAB files use Microsoft MakeCab.exe and on the fly a batch process
This means you can automate the packaging of your products by creating on the fly the tables that will change for each product packaging.
To import the table use MsiDb.exe (provided with the Windows installer SDK).
To validate the packages use Orca or Msival2.exe (both are provided with the Windows installer SDK 2.2, SDK 3.1.4 and SDK 4.5 or above).
The .cub file darice.cub and so on... are also provided with the SDK.
This file contains the ICE (Internal Consistency Evaluators) custom actions needed by Msival2.exe to perform validation.

Related topics: MSI Automation, MSI Command Line, Create MSI Tables, MSI UAC VISTA, MSI Error Table, BootStrapper VISTA, MSP VISTA, Install MSI SDK Tools V3.1.4, Create CAB File, Build MSPs

See more discussions and posts about MSI:
Replacing Non-versioned Files User Data with companion files
New tools to Import VBS JPG - Unable to place file in stream - MSIDB
MSM Validation - ATL.MSM - Documentation
Remove registry info entries for all users in system or just current owner
ARPPRODUCTICON OK for XP not for W2K Add/Remove Programs
Msidb Command Line Folder Path MSI name limitations
Property for All Users Shared Documents or CA?
File Hidden Attribute after installation - Source in CAB files
260 characters limit in shortcut's targets Windows not MSI/Setup Limitation
The MsiZap utility is intended for removal of products installed with MSI that, for some reason, cannot be uninstalled.
You can log an uninstall with: msiexec /x {your product code guid} /l*v mylogfile.log

Here are some of the download links

Is .NET framework is already installed?
Check in using the registry:

HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full\Install
HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full\Version

Example of a Welcome dialog box:
MSI Setup Welcome Frame\

A partial or complete application reinstallation might be required if any files or registry entries associated with any feature have become corrupted or are missing. See more MSI dialogs...

Consider about 3 types of MSI tables:

Localizing a Microsoft Windows Installer package requires modifying the strings displayed by the user interface and may also require adding or modifying product resources. For example, localization may include the addition of international DLLs and localized files to the product.

Task Manager

MSIEXEC's Normal behavior is to launch multiple instances of itself; during a normal install you can expect to see 6-7 different instances of it; usually no more than 3 or 4 concurrently.

Return Home - Index