msp

Patching Multiple Instance Installs with either InstallShield or WiX

孤街醉人 提交于 2019-12-21 18:32:11
问题 I have a project built in InstallShield 12. It is a Web Application that needs to be installed multiple times, and those installations need to be patched. I can create transforms, and patches just fine in both WiX and InstallShield. When I try to patch a transformed install from InstallShield, I get the error: "The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the

Windows installer patch failure - Execute Sequence stops after first action and install process resets

柔情痞子 提交于 2019-12-20 04:34:27
问题 I am seeing an unusual sporadic failure of one of our patches at several customer sites. The final error code is 1648 (No valid sequence could be found for the set of patches), which is occurring because error 2219 (Invalid Installer database format) occurs when attempting to read the summary information stream from one of the patch transforms. But I suspect this is only a side effect of an earlier silent error. Our patches all use the MinorUpdateTargetRTM property so there is really nothing

MSP vs. MSI packaging. Which to use for patches?

青春壹個敷衍的年華 提交于 2019-12-18 02:48:45
问题 Currently I am working on a project which is deployed by using an MSI package. To patch the program, we just deploy another MSI installer package opposed to an MSP. Is this an effective/efficient way to go about this, or should we be deploying an MSP patch package instead? I have had experience with MSI but not MSP. How would I also go about creating an MSP patch? I trawled through the internet and cant seem to find anything. Thanks in advance! 回答1: The choice is really up to you, though MSP

WiX: Patch installer superseding previous versions (1.0.0 -> 1.0.1, 1.0.0 -> 1.0.2, 1.0.1 -> 1.0.2, aso.)

喜夏-厌秋 提交于 2019-12-07 06:59:52
问题 I am trying to provide a simple installer package (MSI) which I want to support with updates (patches) that supersede all previous patches. So I have a MSI V1.0.0 and 2 patches V1.0.1 and V1.0.2. The user should be able to just install the latest patch regardless which previous patches were already applied to the system. My project contains 2 features (Client and Server). The basis of the patch so is always the RTM package (HelloWorld 1.0.msi / HelloWorld 1.0.wixpdb). The generation (build)

WiX: Patch installer superseding previous versions (1.0.0 -> 1.0.1, 1.0.0 -> 1.0.2, 1.0.1 -> 1.0.2, aso.)

拈花ヽ惹草 提交于 2019-12-05 14:15:34
I am trying to provide a simple installer package (MSI) which I want to support with updates (patches) that supersede all previous patches. So I have a MSI V1.0.0 and 2 patches V1.0.1 and V1.0.2. The user should be able to just install the latest patch regardless which previous patches were already applied to the system. My project contains 2 features (Client and Server). The basis of the patch so is always the RTM package (HelloWorld 1.0.msi / HelloWorld 1.0.wixpdb). The generation (build) of all patches work, so the update procedures 1.0.0 -> 1.0.1 and 1.0.0 -> 1.0.2 do, BUT when i try to

Windows installer patch failure - Execute Sequence stops after first action and install process resets

送分小仙女□ 提交于 2019-12-02 04:11:25
I am seeing an unusual sporadic failure of one of our patches at several customer sites. The final error code is 1648 (No valid sequence could be found for the set of patches), which is occurring because error 2219 (Invalid Installer database format) occurs when attempting to read the summary information stream from one of the patch transforms. But I suspect this is only a side effect of an earlier silent error. Our patches all use the MinorUpdateTargetRTM property so there is really nothing to sequence, as any previously installed patched are automatically superseded. Our customers typically

MSP vs. MSI packaging. Which to use for patches?

半腔热情 提交于 2019-11-29 01:53:27
Currently I am working on a project which is deployed by using an MSI package. To patch the program, we just deploy another MSI installer package opposed to an MSP. Is this an effective/efficient way to go about this, or should we be deploying an MSP patch package instead? I have had experience with MSI but not MSP. How would I also go about creating an MSP patch? I trawled through the internet and cant seem to find anything. Thanks in advance! The choice is really up to you, though MSP provides smaller file sizes which can be advantageous for large projects. In particular, this MSDN article