merge-module

I'd like to parse merge module files into two different locations. Is it possible? <Directory Id="TARGETDIR" Name="SourceDir"> <Directory Id="MergeRedirectFolder"> <Component Id="LoggerClient" Guid="*"> <File Id="log4net" Name="log4net.dll" Source="..\..\_Release\log4net.dll" KeyPath='yes' /> <File Id="LoggerLibrary" Name="LoggerLibrary.dll" Source="..\..\_$(var.Configuration)\LoggerLibrary.dll" /> <File Id="app.config" Name="app.config.xml" Source="..\..\_Release\app.config.xml" /> <File Id="msvcr110.dll" Name="msvcr110.dll" Source="c:\windows\sysWoW64\msvcr110.dll" /> </Component> <

I hit numerous errors in Wix 3.0 when I tried to use the msvbvm60.msm merge module: C:\[...]: error LGHT0204 : ICE03: Table: Registry Column: Registry Missing specifications in _Validation Table (or Old Database) C:\[...]: error LGHT0204 : ICE03: Table: Registry Column: Root Missing specifications in _Validation Table (or Old Database) C:\[...]: error LGHT0204 : ICE03: Table: Registry Column: Key Missing specifications in _Validation Table (or Old Database) C:\[...]: error LGHT0204 : ICE03: Table: Registry Column: Name Missing specifications in _Validation Table (or Old Database) C:\[...]:

I have a MSM file from a third party tool. We customize the MSM with a small script and this tool is integrated into our installer and works fine. All modification is done with VBscript using COM and "WindowsInstaller.Installer" But sometimes our support needs just this tool as standalone installer package. Is there a simple way to convert a MSM file into and full installer MSI package on the command line? Using VBscript or the COM Module with the "WindowsInstaller.Installer" is OK. Knowing the way how to to convert it, I would also write a small C++ program doing performing the changes and

Following the excellent suggestion I have moved some variables to WXI file . How do I include it in WXS file ? for reference: http://wix.sourceforge.net/manual-wix2/preprocessor.htm Although this is about wix 2.0 and uses a file with extension .wxs - the game stays the same, as only the "include" element is required to exist in the file. A good article how to use this can be found here: http://weblogs.sqlteam.com/mladenp/archive/2010/02/17/WiX-3-Tutorial-Understanding-main-WXS-and-WXI-file.aspx use <?include ?> preprocessor tag, for example: <?include include.wxi ?> 来源： https://stackoverflow

When products A and B each install several MSIs and some of the MSIs are the same, will uninstalling either A or B affect the other? Does install location matter? Also, what happens when common MSI C's version is higher in Product B and B upgrades C on install? Now uninstalling B will remove the common MSI C which breaks Product A. How do you handle this gracefully without using the Permanent flag? Stein Åsmul The first thing that comes to mind with this question is whether the products in question are decomposed the way they should be. As a general rule all MSI files think they own whatever