Msi installer file structure

If you want to browse MSI files on a Mac, it is also useful to use a file decompression tool. Since the MSI file is not a text format, editing it is not as straightforward as editing most other file formats. Orca can be used in a standalone format without using the entire SDK. Technipages has a copy that you can download. Be careful not to rename the extension on the. This will not change the file type. Only special conversion software can change files from one file type to another.

Sign up today to participate, stay informed, earn points and establish a reputation for yourself! Log in. Structure and features of MSI. Would you like someone to explain the structure and features of the forum?

Were you somehow unable to work out that a section dealing with 'Windows Installer errors' was probably not the place to ask your question? I'm going to be kind Asking questions in so direct a fashion doesn't exactly encourage people to respond. Posted by: pjgeutjens 10 years ago. Posted by: murali. Use google search. The logical structure of packages consists of the following elements: Products : A single, installed, working program or set of multiple programs combined together is a product.

A product is identified by a unique GUID. Features : May contain any number of components and other sub-features. Smaller packages can consist of a single feature. Components : Component is treated by Windows Installer as a unit; can contain program files, folders, registry keys, COM components, and shortcuts. If the Create date is later than the Modified date, the file is considered unmodified, install the file. The installation of a Companion File depends not on its own file versioning information, but on the versioning of its companion parent.

In the case of Companion Files, the installation is skipped only if the parent file has a higher version.

Note that a file that is the key path for its component must not be a companion file because this results in the versioning logic of the key path file being determined by the companion parent file. Nonversioned Files Using Companion Files -A nonversioned file that is associated with a versioned file using the companion mechanism abides by the rules for the versioned file.

The only exception is if the versioned file on the computer and the versioned file being installed have the same version and language but the companion file is missing on the computer. In this case the companion file being installed is used even though the versioned file on the computer is used.

Rules are Global—The rules for determining when to install a file reside in one place within the installer and are global, meaning they apply to all files equally.