Here are some component guidelines which you need to follow in your application MSI. This will solve many issues like installation fix and automatic package repairs.

Always remember,

• HKLM + HKCU in same component are not allowed
• HKCR + HKCU in same component are not allowed
• HKCU + Files in same component are not allowed. (Exception where the files are going to user profiles and key path is HKCU key path)

Also, when you design a custom component having HKCR or HKLM components, do check the Auto increment option; this helps the machine maintain a stable state.

When we create a Windows Installer file by using Visual Studio .NET, we do not have the option to designate that your package is to be advertised.

We can advertise the package only by using a command-line option during the installation. At the command prompt, we can explicitly list the features that we want to advertise or we can advertise all the features.

To explicitly list the features, we must use a command that is similar to the following:

Msiexec.exe /i {PATH}\.msi ADVERTISE=Feature1,Feature2,Feature3

If we want to use this command, the features must be present in the Feature column of the Feature table in the Windows Installer file.

To advertise all the features, we must use a command that is similar to the following:

Msiexec.exe /i {PAth}\.msi ADVERTISE=ALL...

The purpose of a deferred execution custom action is to delay the execution of a system change to the time when the installation script is executed.

This differs from a regular custom action, or a standard action, in which the installer executes the action immediately upon encountering it in a sequence table or in a call to MsiDoAction.

A deferred execution custom action enables a package author to specify system operations at a particular point within the execution of the installation script.

The installer does not execute a deferred execution custom action at the time the installation sequence is processed. Instead the installer writes the custom action into the installation script.

1. Should be placed between install initialize and install finalize.
2. Does not have...

I stumbled upon this site and wanted to share it with you. It contains MSI tips and notes - very handy for beginners.

http://www.prairienet.org/~pops/msi_tips.html

It covers and explains the below topics in a nice and simple manner.

• Expanding properties at run time
• Avoiding custom actions by using the -File tables
• Fixing up a failed uninstall
• File versions vs. ProductVersion
• Some property names (silly)
• Add or Remove Programs properties
• Logging switches
• Merge modules and properties
• AppSearching
• Launching a batch file in a custom action
• "Sorry, but..."
• Taking inventory of...