merge-module

问题 I am using WiX for building MSI and MSP. In my MSI, I have an MSM file present. I made some changes to the files in the MSM and re generated the same. Now I wanted to create a patch/MSP with the change in MSM included. Please help me to create a MSP with the updated MSM file. 回答1: An MSP - a Windows Installer Patch - is merely a distribution / packaging mechanism for an MSI update that is already working as a full package . Hence the process of making an MSP that contains the updated files -

问题 I've been using VS 2015 for a while now and just upgraded to VS 2017 when it launched yesterday (2017-03-07). I installed with only the .NET desktop and C++ desktop workflows, without changing any other individual components. I'm considering migrating my C++ projects to the 2017 toolchain (version "141" apparently? 2015 was "140"). I need to use the VC merge modules for my installer, so I looked in the C:\Program Files (x86)\Common Files\Merge Modules folder, but that folder only contains

问题 I have 2 custom installshield merge modules. I am using these merge modules inside a installshield project. Now I want when user run main installshield package then he should be able to select the installation path of 2 merge modules him self. Is it possible in installshield merge module? 回答1: You need to create 2 features in the installshield project, with 1 merge module in each feature. Then make sure the Custom Destination dialog is in your sequence, so the user can select the install path

问题 I'm trying to use a merge module in my setup-project. But it seems like there are dependencies in it that require earlier versions of a couple of merge modules than I have (I've got VS2008). I need these files from VS2005: Microsoft_VC80_ATL_x86.msm Microsoft_VC80_CRT_x86.msm Microsoft_VC80_MFC_x86.msm policy_8_0_Microsoft_VC80_ATL_x86.msm policy_8_0_Microsoft_VC80_CRT_x86.msm policy_8_0_Microsoft_VC80_MFC_x86.msm Could anyone please point me to a place where I can download them or make a zip

问题 I have two custom actions, one of which I'd like to execute when my product is installed and the other when it is uninstalled. My custom action is currently called from a merge module after the "InstallFinalize", but this happens for both install and uninstall. I've tried adding the "NOT INSTALLED AND NOT UPGRADINGPRODUCTCODE" condition, but that gave me an error: Error 2762. Cannot write script record. Transaction not started. I've also tried attaching to other actions (for example,

问题 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:

问题 I can find plenty of info on how msi upgrades. E.g. info about minor upgrade, small upgrade, major upgade, and their use case and limitations. However, I cannot find info on the upgrade behavior of merge module, such as: It seems like msm does not have any way to specify minor, small, or major upgrade. So which way it behaves in? Does it uninstall old version first or only update changed files? Is there any way to specify from which version it can be upgraded like msi? Can I add/remove/rename

问题 I can find plenty of info on how msi upgrades. E.g. info about minor upgrade, small upgrade, major upgade, and their use case and limitations. However, I cannot find info on the upgrade behavior of merge module, such as: It seems like msm does not have any way to specify minor, small, or major upgrade. So which way it behaves in? Does it uninstall old version first or only update changed files? Is there any way to specify from which version it can be upgraded like msi? Can I add/remove/rename

问题 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=

问题 I read quit a few Stackoverflow Questions about building mergemodules via commandline but all of them were accepted when either somebody suggested to use devenv for compilation or use Dark to create wix-files from existing msi files. Considering the following: VisualStudio isn't installed on the buildserver I have to use. I am using nant + msbuild to compile the solutions I would like to compile mergemodules from .vdproj (because Visual Studio detects dependencies automatically) and create a