\| ContactEZ.net International Bilingual Services |
ContactEZ.net |
For contextual information you may need to first read the topic Do not spend thousands of dollars to purchase packaging software!
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).
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
Is .NET framework is already installed?
Check in the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\policy\v1.1
If the location of the Framework is needed then check:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\InstallRoot
Or check:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v1.1.4322
Example of a Welcome dialog box:
\
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.
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.
For more information:
Importing VBS JPG - Unable to place file in stream, Replacing Non-versioned Files - User
Data, ProgID table produces error during run time - Validation, Remove registry info
entries for all users in system or just owner?, MSM Validation - ATL.MSM, and more... see
my posts with ContactEZ.net on group:microsoft.public.platformsdk.msi
Windows Installer (Microsoft)
Tek-Tips
Forums member name dgschnei
Some keywords you can use to search topics: instmsiW.exe, orca, Msival2, darice
| About Dominique Gérard Schneider since 1995 - Developing solutions that really help! | ||
| Participation on Google ContactEZ.net on YouTube Tek-Tips Forums dgschnei |
Listed since 1996 ixquick Community Services platform sdk dgschnei |
Cooperation About Me Gifts Home Decoration |
Tek-Tips Forums, and platform sdk (member name dgschnei).