/ 
Win32-MSI-HighLevel-1.0001
River stage zero No dependents
/ Win32::MSI::HighLevel

NAME

Win32::MSI::HighLevel - Perl wrapper for Windows Installer API

VERSION

Version 1.0001

SYNOPSIS

use Win32::MSI::HighLevel;

my $filename = 'demo.msi';

unlink $filename;
my $msi = HighLevel->new (-file => $filename, -mode => Win32::MSI::HighLevel::Common::kMSIDBOPEN_CREATE);

$msi->addFeature (
    -Feature => 'Complete',
    -Title => 'Full install', -Description => 'Install the whole ball of wax'
    );

$msi->createTable (
    -table => 'Feature',
    -columnSpec => [
        Feature  => ['Key', 'Identifier'], Feature_Parent => 'Identifier',
        Title => 'Text(64)', Description => 'Text(255)',
        Display => 'Integer', Level => 'Integer',
        Directory_ => 'Directory',
        Attributes => 'Integer',
        ]
    );

$msi->writeTables ();
$msi->commit ();
$msi = 0;

DESCRIPTION

Win32::MSI::HighLevel allows the creation (and editing) of Microsoft's Windows Installer technology based installer files (.msi files).

The initial impetus to create this module came from trying to find an automated build system friendly way of creating Windows installers. This has been very nicely achieved, especially as the core table information can be provided in text based table description files and thus managed with a revision control system.

Windows Installer files are simply database files. Almost all the information required for an installer is managed in tables in the database. This module facilitates manipulating the information in the tables.

Obtaining a database object

MSI::HighLevel::new ($filename, $mode) returns a new database object. $mode may be one of:

$Win32::MSI::MSIDBOPEN_READONLY

This doesn't really open the file read-only, but changes will not be written to disk.

$Win32::MSI::MSIDBOPEN_TRANSACT

Open in transactional mode so that changes are written only on commit. This is the default.

$Win32::MSI::MSIDBOPEN_DIRECT

Opens read/write without transactional behaviour.

$Win32::MSI::MSIDBOPEN_CREATE

This creates a new database in transactional mode.

HighLevel Methods

Generally sample usage is provided for each method followed by a description of the method, then followed by any named parameters recognised by the method.

Most methods require named parameters. Named parameters with an uppercase first letter map directly on to table columns. Named parameters with a lower case first letter generally use contextual information to simplify using the method.

Table column names with a trailing _ are key columns for their table.

new

Create a new HighLevel instance given a file and open mode.

my $msi = HighLevel->new (-file => $file, -mode => Win32::MSI::HighLevel::Common::kMSIDBOPEN_DIRECT);
-file: required

the .msi file to open/create

-mode: optional

parameter - the open/create mode. Defaults to Common::kMSIDBOPEN_TRANSACT

Must be one of:

Win32::MSI::HighLevel::Common::kMSIDBOPEN_READONLY

open for read only assess only

Win32::MSI::HighLevel::Common::kMSIDBOPEN_TRANSACT

open existing file for transacted access

Win32::MSI::HighLevel::Common::kMSIDBOPEN_DIRECT

open existing file for direct (non-transacted) access

Win32::MSI::HighLevel::Common::kMSIDBOPEN_CREATE

create a new file for transacted access (see the commit member below)

Win32::MSI::HighLevel::Common::kMSIDBOPEN_CREATEDIRECT

create a new file for direct (non-transacted) access

-sourceRoot: optional

Provide the (absolute) source directory that corresponds to the TARGETDIR directory on the target system. Directories on the target system have the same relative path from TARGETDIR as directories on the source system have to the source folder.

-sourceRoot defaults to the cwd.

-targetRoot: optional

Provide the default (absolute) target directory for the install. Note that the actual location can be set at install time by the user.

autovivifyTables

$msi->autovivifyTables (qw(Components Dialog Feature Properties));

Ensure that a list of tables exist. Create any tables in the list that do not exist already.

This should be called after populateTables has been called if you are not dealing with a new .msi file.

close

Close the database. Generally close is not required to be called explicitly as the database should close cleanly when the HighLevel object is destroyed.

$msi->close ();

commit

commit is used to update the database in transacted mode. Although the .msi database API provides a commit which must be called in transacted mode, there doesn't seem to be anything like an explicit rollback! An implicit rollback happens when the database is closed without a commit however.

$msi->commit ();

addAppSearch

Add an entry to the AppSearch table.

-Property: required

Property that is set by the AppSearch action when it finds a match for the signature.

-Signature_: required

An entry into the Signature table (for a file) or a directory name.

Note that support is not currently provided for adding an entry to the Signature table!

addBinaryFile

Add a binary file to the installation.

-Name: required

Id to be used as the key entry in the binary file table. This entry must be unique.

-file: required

Path to the file to be added on the source system.

addCab

Adds a cabinet file the the Cabs table and updates the media table to match.

This routine is primaraly used by createCabs and should not generally be required by users.

-name: required
-file: required
-disk: required
-lastSeq: required

addComponent

addComponent adds a component associated with a specific Directory table entry and a group of files.

my $newId = $msi->addComponent (-Directory_ => 'wibble');
-Directory_: required

Identifier for the directory entry associated with the component.

-features: required

Array of Feature table Feature identifiers that the component is referenced by.

This parameter is required to generate appropriate entries in the FeatureComponents table.

-File: optional

Optional file name for the key file associated with the component.

If the directory is to be used in the CreateFolder table then the file name should be omitted and the directory name will be used as the key for the component.

-requestedId: optional

Desired id for component. If there exists a component with the same Id already then the suggested Id will be used as a base so generate a new Id.

addCreateFolder

addCreateFolder adds an entry to the create folder table for the given folder. Component and directory table entries will be generated as required.

my $entry = $msi->addCreateFolder (-Folder => $dirPath);
-FolderPath: required

Path name of the folder to create on the target system.

-sourcePath: optional

-sourcePath may be provided to build a directory tree on the target system matching a directory tree on the source system. The folder provided by -FolderPath must match the folder provided by -sourcePath and will be the root of the directory tree created on the target system.

addCustomAction

Add an entry to the custom action table.

$msi->addCustomAction (
    -Action => 'InstallDriver',
    -Type   => 3074,
    -Source => 'DriverInstaller',
    -Target => "[CommonFilesFolder]\\$Manufacturer\\driver.inf",
    );

This provides fairly raw access to the CustomAction table and is only part of the work required to set up a custom action. See the CustomAction Table section in the documentation referenced in the See Also section for further information.

-Action: required

Id for the custom action.

-Type: required

A number comprised of various bit flags ored together.

-Source: required

A property name or external key into another table. This depends on the Type.

-Target: required

Additional information depending on the Type.

addDirectory

addDirectory adds a directory with a specified parent directory to the directory table.

my $entry = $msi->addDirectory (-Directory => $dir, -DefaultDir => $def, -Diretory_Parent => $parent);
-DefaultDir: optional
-Directory: optional

Identifier for the directory entry to create. This identifier may be the name of a property set to the full path of the target directory.

-Diretory_Parent: required

This must be a Directory table Directory column entry or undef. If -Diretory_Parent is undef or the same value as -Directory the added entry is for a root directory. There must only be one root directory in the Directory table.

Except in the case of a root directory entry, the value given for -Diretory_Parent must already exist as a -Directory entry in the Directory table.

-target: optional
-source: optional

addDirPath

addDirPath is not fully implemented should not be used. Use multiple calls to addDirectory instead.

addMsiDriverPackages

Adds a device driver package to the installer.

$msi->addMsiDriverPackages (-Component => 'InstallDriver', -Flags  => (2 | 4));
-Component: required

Id for the custom action.

-Flags: optional

A number comprised of various bit flags ored together.

See the MsiDriverPackages Custom Table Schema topic in the Windows Driver Kit: Device Installation documentation for the use of this parameter. the default value is 0.

-Sequence: optional

Determines driver installation order. Packages are installed in increasing order of sequence number. Packages with the same sequence value are installed in arbitary order.

addFeature

Add an installation feature. Parent features must be added before child features are added. Multiple root features are allowed and provide different installation configurations.

my $root = $msi->addFeature (-name => 'Complete', -Title => 'Full install');

The following parameters are recognised by addFeature

-Attributes: optional

-Attributes is set to msidbFeatureAttributesFavorLocal by default. For a discussion of the -Attributes parameter see the Feature Table documentation (see See Also below).

-Description: optional

A textual description of the feature shown in the text control of the selection dialog.

-Directory_: optional

Directory associated with the feature that may be configured by the user at install time. The directory must already have been added with addDirectory, addDirPath or createDirectory.

-Display: optional

Determines the display state and order of this feature in the feature list.

If -Display is not provided it will be set so that the new feature is shown after any previous features and is shown collapsed.

If -Display is set to 0 it is not shown.

If -Display is odd is is shown expanded. If -Display is even it is shown collapsed.

Display values must be unique.

-Feature_Parent: optional

Identifier for the parent feature. If this parameter is missing a root feature is generated.

-Level: optional, default = 3

Initial installation level for the feature. See the Feature Table documentation for a discussion of installation level (see See Also below). For a single feature install a value of 3 (the default) is often used. 0 may be used for a feature that is not to be installed at all.

-name: required

The name of the feature to add.

-Title: optional

The name of the feature to add.

addFile

addFile is used to add a file to be installed. Adding a file associated with a feature (or features) updates the File and DiskId tables and may update the Component, FeatureComponent and DuplicateFile tables.

my $file = $msi->addFile (-source => $filepath, -featureId => 'Complete');

Default values are determined for -Sequence and -Version from the source file which must be available when addFile is called.

-cabFile: optional

Provide the name of a cab file the current file should be added to. By default the file is added to an internally generated cab file.

If the file is to not to be compressed and stored internally in a cab file -cabFile should be set to undef.

See also "createCabs".

-featureId: required

Id of the Feature that the file is to be installed for.

-fileName: required

Name of the file to be installed. Note that a long file name should be given: addFile generates the required short file name.

-forceNewComponent: optional

If present this parameter forces a new component to be generated. The value is used as a suggested component name.

-isKey: optional

File is a key file for a component. Required to be set true if there is to be a shortcut to the file. If the file is a PE format file (.exe, .dll, ...) -isKey is implied.

-Language: optional

Specify the language ID or IDs for the file. If more than one ID is appropriate use a comma serparated list.

If this parameter is omitted the value '1033' (US English) is used. To specify that no ID should be used (for font files for example) us an empty string.

-Sequence: optional

Determines the order in which files are installed. By default files are installed in the order that they are added. Setting -Sequence for a file sets the install position for that file and any files added subsequently.

If setting the sequence number for a file causes a collision with any file already added the previously added files are moved later in the install sequence (their sequence number is increased). Note that any subsequently added files may also cause previously added files to be installed later. In other words, setting -Sequence for a file allows a group of files to be inserted at a particular place in the install order.

Use:

-Sequence => undef

to reset to adding files at the end of the install order.

-sourceDir: required

Path to the directory containing the file to be installed.

-skipDupAdd: optional

Skip adding the file if an entry already exists for it.

-targetDir: optional

Path to the directory the file is to be installed to on the target system.

If -targetDir is not provided the target directory will be set to be in the same relative location as the source directory is to the source root directory. -sourceDir must be in the directory tree below the source root directory if -targetDir is not provided.

-Version: optional

-Version should only be set to specify a companion file (see "Companion Files" in the SDK documentation). For a versioned file the version number is obtained from the file's version resource.

addFiles

addFiles is not implemented. Use multiple calls to addFile instead.

There are design issues concerning the implemenation of addFiles and the management of components. A mechanism for handling exclusions should also be provided.

addIconFile

Add an icon file to the installation.

my $iconId = $msi->addIconFile ('path/to/unique_file_name.ico');

Note that an internal ID is generated from the file name (excluding the path to the file). The file name must thus only contain alphanumeric characters, periods and the underscore character.

Two icon files that differ only in their path, but have the same name will cause grief (only one of the files will be used). This condition is not checked for!

The generated internal Id is returned and may be used for the -Icon_ parameter required in other tables.

The file must exist at the time that addIconFile is called.

addIconFile may be called multiple times with the same file

addInstallExecuteSequence

Add an entry to the custom action table.

$msi->addInstallExecuteSequence (
    -Action    => 'InstallDriver',
    -Condition => 'NOT MYDRIVERINSTALLED AND NOT Installed',
    -Sequence  => 3959,
    );

This provides fairly raw access to the CustomAction table and is only part of the work required to set up a custom action. See the CustomAction Table section in the documentation referenced in the See Also section for further information.

-Action: required

Id for the action. This must be either a built-in action or a custom action.

A matching entry must exist in the CustomAction table if this is a custom action.

-Condition: required

A conditional expression that must evaluate true at run time for the step to be executed.

-Sequence: required

Sequence position for execution of this action.

addInstallUISequence

Add an entry to the custom action table.

$msi->addInstallUISequence (
    -Action    => 'SetDefTargetDir',
    -Condition => '',
    -Sequence  => 1100,
    );
-Action: required

Id for the action. This must be either a built-in action or a custom action.

A matching entry must exist in the CustomAction table if this is a custom action.

-Condition: required

A conditional expression that must evaluate true at run time for the step to be executed.

-Sequence: required

Sequence position for execution of this action.

addLaunchCondition

Add an entry to the custom action table.

$msi->addLaunchCondition (
    -Condition => 'NOT Version9X',
    -Description  => 'Windows versions prior to XP are not supported.',
    );

This provides fairly raw access to the CustomAction table and is only part of the work required to set up a custom action. See the CustomAction Table section in the documentation referenced in the See Also section for further information.

-Condition: required

A conditional expression that must evaluate true at run time for the install to proceed.

-Description: required

Error text shown if the launch condition evaluates false.

addMedia (see also setProperty)

Add a cabinet file to the Media table.

$msi->addMedia (-Cabinet => '#cab1', -DiskId => 1, -LastSequence => 20);

If all the files required by the install are to be part of the .msi file then addMedia can be ignored - createCabs does all the work required.

-Cabinet: optional

Name of the cabinet file.

A # as the first character in the name indicates that the cabinet file will be stored in a stream in the .msi file. In this case the name is case sensitive.

If the first character in the name is not a # then the name must be given as a short file name (8.3 format) and the cabinet is stored in a separate file located at the root of the source tree specified by the Directory Table.

-DiskId: required

A number (1 or greater) that determines the sort order of the media table.

-LastSequence: required

Sequence number of the last file in this media.

-DiskPrompt: optional

Name (on the lable for physical media) used to identify the physical media associated with this media entry.

-Source: optional

Source to be used for patching.

-VolumeLabel: optional

Volume label to be used to identify physical media.

addProperty (see also setProperty)

Add a property value to the Property table. A new property id is generated based on the supplied id if a property of the same name exists already.

$msi->addProperty (-Property => 'Manufacturer', -Value => 'Wibble Corp.');

The actual property id used is returned.

-Property: required

Suggested property name

-Value: required

Property value

addRegistry

Add a registry entry.

$msi->addRegistry (
    -root => HighLevel::msidbRegistryRootClassesRoot,
    -Component_ => 'Application',
    -Key => '.app',
    -Name => undef,
    -Value => 'MyApp'
    );
-Component_: required

Id of the component controling installation of the registry value.

-Key: required

Key path which may include properties but must not start or end with a backslash (\).

-Name: optional
-Root: required
-Value: required

Registry value to add.

addRegLocator

Add a RegLocator table entry.

$msi->addRegLocator (
    -Signature_ => 'MyDriver',
    -Root       => HighLevel::msidbRegistryRootLocalMachine,
    -Key => 'SYSTEM\CurrentControlSet\Control\Class\{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}',
    -Name => 'Class',
    -Type => HighLevel::msidbLocatorTypeRawValue,
    );
-64Bit: optional

Set to search the 64-bit portion of the registry. The 32-bit portion of the registry will not be searched if -64Bit is set.

-directory: optional

A key into the Directory table to be set from the registry.

One of -directory, file and -property is required.

-file: optional

A key into the File table to be set from the registry.

One of -directory, file and -property is required.

-Key: required

Key path.

-Name: optional

Registry value name. If omitted the default value is used.

-property: optional

A key into the Property table to be set from the registry.

One of -directory, file and -property is required.

-Root: required

One of:

msidbRegistryRootClassesRoot: HKEY_CLASSES_ROOT
msidbRegistryRootCurrentUser: HKEY_CURRENT_USER
msidbRegistryRootLocalMachine: HKEY_LOCAL_MACHINE
msidbRegistryRootUsers: HKEY_USERS

addShortcut

The following parameters are recognised by addShortcut:

-Arguments: optional

The command line arguments for the shortcut.

-Component_: optional (see also -target and -Target)

The id for the Component table entry which determines whether the the shortcut will be deleted or created. The shortcut is created if the component has been installed and is deleted otherwise.

If -Component_ is not provided the component associated with -target or -Target will be used.

-Description

The localizable description of the shortcut.

-Directory_: optional (see also -location)

The id for the Directory table entry which specifies where the shortcut file will be created. The Directory entry need not exist until writeTables is called and is not checked.

One only of -location and -Directory_ must be provided.

-featureId

The feature the shortcut is installed by.

-Hotkey

The hotkey for the shortcut. The low-order byte contains the virtual-key code for the key, and the high-order byte contains modifier flags.

-folderTarget: optional (see also -target and -Target)

The folder pointed to by the shortcut. Note that this folder must already have been provided using addDirectory, addDirPath or createDirectory.

One only of -folderTarget, -target and -Target must be provided.

-location: optional (see also -Directory_)

The directory where the shortcut file will be created. Note that the directory must already have been added with addDirectory, addDirPath or createDirectory.

The directory provided will be searched for in the Directory table to find the directory id to be used for -Directory_.

One only of -location and -Directory_ must be provided.

-Name: required

Name to be shown for the shortcut. Note that the name need not be unique.

-Shortcut: optional

Suggested internal id to be used for the shortcut. Note that if there is another shortcut with the same id already a new id will be generated by appending a number to the given id. The id actually used is returned.

If -Shortcut is omitted a suitable id will be generated from the -Name value.

-Target: optional (see also -folderTarget and -target)

The Feature id or a Property id that specifies the target of the shortcut.

If a Feature id is provided the target is the key file of the Component_ table entry associated with the Feature.

If a Property id is provided the target is the file or directory specified as the value of the property.

One only of -folderTarget, -target and -Target must be provided.

-target: optional (see also -folderTarget and -Target)

The file pointed to by the shortcut. Note that this file must already have been provided using addFile or addFiles.

One only of -folderTarget, -target and -Target must be provided.

-WkDir: optional (see also -wkdir)

The Directory id that specifies the working directory for the shortcut.

One only of -wkdir and -WkDir may be provided.

-wkdir: optional (see also -WkDir)

The working directory for the shortcut.

A directory table will be created if required.

One only of -wkdir and -WkDir may be provided.

createCabs

Creates the cab files as required from the files that have been added with "addFile" or "addFiles".

$msi->createCabs ();

Note that createCabs must be called after all files have been added and before "writeTables" is called.

Note too that makecab.exe must be available on the system being used. With versions of Windows from Windows 2000 on makecab.exe seems to be provided with the system so this should not generally be an issue. If createCabs generates a 'makecabs.exe not found' error copy makecabs.exe into the working directory or add the path to makecabs.exe to the PATH environment variable.

createCabs updated the Media table as appropriate.

createTable

Creates a new database table.

my $table = $msi->createTable (-table => 'Feature');
my $table = $msi->createTable (
    -table => 'Properties',
    -columnSpec => [
        Property => [qw(Key Identifier(72) Required)],
        Value => [qw(Text(0) Required)],
        ]
    );
-columnSpec: optional

Specification for the table's columns. This is required for tables that Win32::MSI::HighLevel doesn't handle by default.

Note that custom tables may be added to the installer file.

The column specification comprises an array of column name => type pairs. Most of the types mentioned in the MSDN documentation are recognised, including:

AnyPath:
Cabinet: CHAR(255)
DefaultDir: CHAR(255)
Directory: CHAR(72)
FileName: CHAR(128) LOCALIZABLE
Formatted: CHAR(255)
Identifier: CHAR(38)
Integer: INT
Long: LONG
Property: CHAR(32)
Required: NOT NULL
Shortcut: CHAR(255)
Text: CHAR(255) LOCALIZABLE
UpperCase: CHAR(255)

Where the default type includes a size (number in parentesis) a different size may be supplied by including it in parentesis following the type:

Text(0)
-table: required

Name of the table to create.

dropTable

Removes a database table.

my $table = $msi->dropTable ('Feature');

expandPath

Expand a path including system folder properties to a path with the system folders resolved by examining Directory table entries.

my $path = expandPath ($filePath);

expandPath returns a long path.

exportTable

Saves a database table in a .csv file format.

my $table = $msi->exportTable ('Directory', '.\Tables');

Important! You must writeTables before calling exportTable to ensure that the database version of the table matches the internal cached version.

The sample code would export the Directory table as the file 'Directory.idt' to the sub-directory Tables in the current working directory.

If the table includes streams a sub-directory to the directory containing the exported file will be created with the same base name as the table. A file for each stream will then be created in the sub-directory. The created files will have the extension '.idb'.

Note that the table name _SummaryInformation may be used to write out the Summary Information Stream.

Also note that the exported file format is ideal for management using a revision control system.

See also importTable.

getComponentIdFromFileId

Return the component Id for the given file Id.

my %entry = getComponentIdFromFileId ('Wibble.txt');

This call does not create a component or file entry. It returns null if there is not a matching file id.

getComponentIdForDirId

Return the component Id for the component that has a null KeyPath and a Directory_ value matching the directoty id passed in.

my %entry = getComponentIdForDirId (-Directory => 'Wibble', -features => ['Complete']);

A component is created if there is not an appropriate existing component.

-Directory: required

Directory Id to find (or create) a matching component Id for.

-features: required

List of features that reference the component associated with the directory.

getParentDirID dirId

Returns the parent Directory table id given an existing directory id.

my $dirId = $msi->getParentDirID ('WibbleApp');

If the dirId passed in does not exist an undef will be returned, otherwise a string (which may be empty for a root dir) will be returned.

getProduct

Return a string containing product and major version information.

my $productString = $msi->getProduct ();

getProductCode

Return a GUID as a string containing product code for the installer.

my $productGUID = $msi->getProductCode ();

If a product code does not yet exist it will be generated as the MD5 sum of the ProductName, ProductLanguage, ProductVersion and Manufacturer property values.

getProperty

Return the Property value for the given property name. Returns undef of the property entry doesn't exist.

my %entry = $msi->getProperty ($propName);

getTableEntry

Return a reference to the table column data for a given table entry.

my $entry = $msi->getTableEntry ('File', {-File => 'wibble.exe'});

Returns undef if the table or key doesn't exist.

If fields within the $entry hash ref are edited updateTableEntry must be called.

A degree of caution is advised in using this member. Very little checking can be performed on the results of editing the hash returned. Generally errors will result in failures at writeTables time.

getTargetDirID targetpath [public]

getTargetDirID returns a Directory table id given an install time target file path. Entries in the Directroy table will be created as required to generate an appropriate id.

my $dirId = $msi->getTargetDirID ('[ProgramFilesFolder]\Wibbler\WibbleApp');

An existing Directory table entry may be used as the first element of a directory path. If an existing Directory table entry is used it must be the first element of the directory path. Relative paths are with respect to the target install directory (TARGETDIR).

Where existing Directory table entries match a given path prefix the existing entries are used to reduce proliferation of table entries.

getTargetDirID generally takes a single unnamed parameter which is the install time (target) path to match.

Note that the paths may use either \ or / delimiters. All path components are assumed to be long (not short "filename"). Short "filenames" will be generated as required.

An optional (second) boolean parameter may be provided to indicate that the Directory is public. That is, that at install time the user may change the install location for the directory. If a true value is provided as the second parameter the directory Id is forced to upper case to make the entry a public directory entry.

The following system folder properties may be used directly as shown in the sample code above:

CommonAppDataFolder

Full path to the file directory containing application data for all users

CommonFilesFolder

Full path to the Common Files folder for the current user

StartMenuFolder

Full path to the Start Menu folder

haveDirId dirName

Returns a reference to the Directory table entry for given directory Id if it exists or undef otherwise.

my $dirEntry = $msi->haveDirId ('Wibble');

importTable

Imports an exported database table in a .csv file format.

my $table = $msi->importTable ('Directory', '.\Tables');

$msi->writeTables ();
$msi->populateTables ();

Important! You should writeTables and then populateTables following calling importTable to ensure the cached table information matches the database version.

The sample code would import the Directory table from the file 'Directory.idt' in the Tables sub-directory of current working directory.

Note that the table name _SummaryInformation may be used to import the Summary Information Stream.

populateTables

Read the current .msi file and build an internal representation of it.

registerExtension

Add table entries to register a file extension and hook it up to an application. Note that Extension, ProgId and Verb tables may be affected by this call depending on the parameters supplied.

$msi->registerExtension (
    -Extension => 'myext',
    -Component_ => $componentId,
    -ProgId => 'MyApp.Data.1',
    -Feature_ => $featureId,
    -Description => 'MyApp data file',
    -Verb => 'Open',
    -Argument => '%1',
    );
-Argument: optional

Command line argument to be used when launching the application. %1 may be used to pass the file on the command line.

-Component_: required

Id of the component that controls installation of the extension.

-Extension: required

File extension (excluding the .) that is to be registered.

If multiple extensions need to be mapped to the same ProgId an array reference may be used for the value of this parameter:

$msi->registerExtension (..., -Extension => [qw(myext1 myext2)], ...);
-Description: optional

Text that is shown in explorer for the file type.

-Feature_: required

Feature that supplies the application associated with the extension.

-Icon_: optional

Entry in the Icon table that supplies an icon used for files of this type.

-iconFile: optional

Path to the file containing the icon referred to by -IconIndex.

Note that the file name must be a unique icon file name independently of the path and must only contain alphanumeric characters, periods and underscores. This is because registerExtension forms an ID that is used internally to identify the specific icon file. Multiple extensions may use the same icon file so it is important that registerExtension can generate a one to one mapping between the file name and the internally generated ID.

-IconIndex: optional

Index to the icon resource in the file provided by the -Icon_ table entry (which may be provided using -iconFile).

-MIME_: optional

MIME table Content Type entry specifying the MIME type of the contents of files of this extension.

A -MIMECLSID is required if this parameter is supplied.

-MIMECLSID: optional

CLSID for the COM server that is associated with the MIME type for files of this extension type.

This parameter is required only if a -MIME_ parameter is provided.

-ProgId_: optional

ProgId table entry for the application associated with the file extension.

Note that several extensions may reference the same ProgId. However, if more than one extension references the same ProgId the -Description and -Icon* parameters for the first registered (or pre-existing) entry is used.

-ProgId_Parent: optional
-Verb: optional

Explorer's right click menu entry text for an action associated with files of this type.

If a -Verb parameter is supplied a -ProgId_ is required also.

setProduct

Set various product related information.

$msi->setProperty (-Language => 1033, -Name => 'Wibble', -Version => '1.0.0', =Manufacturer => 'Wibble Mfg. Co.');

For a new installer this should be called before any addComponent calls are made as information from the product details is used to generate information required to generate component table entries.

Property table entries are generated or updated by this call. In addition to the properties discussed in conjunction with the parameters described below, a ProductCode value is generated and added to the Property table.

The product code value is returned.

-Name: required

Product name.

-Manufacturer: required

Manufacturer's name.

-Language: required

Language code (LangId).

-Version: required

Product version

setProperty (see also addProperty)

Set a property value in the Property table. The property is added if it didn't exist already.

$msi->setProperty (-Property => 'Manufacturer', -Value => 'Wibble Corp.');

The previous value is returned or undef is returned if a new property is added.

-Property: required

Property name

-Value: required

Property value

setTableEntryField

Sets specified fields in an existing table entry.

$msi->setTableEntryField (
    'Control',
    {-Dialog_ => 'Start_Installation_Dialog', -Control => InstallNow},
    {-Text => 'Install'}
    );

The first hash ref parameter must include entries for all the table's key fields.

Note that this method provides fairly raw access to table entries and does not perform very much validation. In particular fields that are linked to other tables should not be altered using setTableEntryField!

updateTableEntry

Update the table column data for a table entry obtained using getTableEntry.

my $entry = $msi->getTableEntry ('File', {-File => 'wibble.exe'});

$entry->{-File} = 'Wibble.exe';
$msi->updateTableEntry ($entry);

Use with caution. In particular, do not create new keys in the hash.

view

Creates a Win32::MSI::HighLevel::View into the database.

my $view = $msi->view (-table => 'Feature');

Generally other ways of manipulating the database are more useful than through a view. However a Win32::MSI::HighLevel::View can be created to search tables for specific information using the -columns, -where, -order and -tables parameters to return selected records.

writeTables

Write changes that have been made to the tables using the add* members. Until writeTables is called the changes that have been made are cached in memory. writeTables writes these changes through to the .msi database in preparation for a "commit".

REMARKS

This module depends on Win32::API, which is used to import the functions out of the msi.dll. Microsoft's Windows Installer technology must be installed on your system for this module to work.

BUGS

Please report any bugs or feature requests to bug-win32-msi-highlevel at rt.cpan.org, or through the web interface at http://rt.cpan.org/NoAuth/ReportBug.html?Queue=Win32-MSI-HighLevel. I will be notified, and then you'll automatically be notified of progress on your bug as I make changes.

SUPPORT

This module is supported by the author through CPAN. The following links may be of assistance:

ACKNOWLEDGEMENTS

This module was inspired by, and is derived in part from Philipp Marek's http://search.cpan.org/dist/Win32-MSI-DB.

AUTHOR

Peter Jaquiery
CPAN ID: GRANDPA
grandpa@cpan.org

COPYRIGHT & LICENSE

This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

The full text of the license can be found in the LICENSE file included with this module.

SEE ALSO

Microsoft MSDN Installer Database documentation: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/installer_database.asp