msi-patch

问题 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 have few locations on the field for which the initial .msi is same having about 2000 files (of multiple file types). However, I will have to send patches to few of the locations depending on the need so the patch should consist of fewer files (sometimes only 1 file as a fix). I am unable to create a patch (.msp) with just one single file or few files that I want to add/update but have to include all the original set of files as well. Can this be accomplished by any means? Please help !!

问题 I have created a patch for my product using Installshield. When I apply the patch the product files get updated successfully. However, when trying to uninstall the patch it uninstalls or removes successfully the newly added dlls to the patch from the target m/c, but somehow some dlls or exe which got modified due to the patch are not reverting back upon uninstallation of the patch. When I see the version, date and time of some of the dlls are the date on which patch was applied and also the

问题 I have created a patch for my product using Installshield. When I apply the patch the product files get updated successfully. However, when trying to uninstall the patch it uninstalls or removes successfully the newly added dlls to the patch from the target m/c, but somehow some dlls or exe which got modified due to the patch are not reverting back upon uninstallation of the patch. When I see the version, date and time of some of the dlls are the date on which patch was applied and also the

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

问题 I created an installer, deployed to our test environment and got an error due to a missing dll (it was not included in the wsx file). Is it possible to create a MSP patch to ship the missing dll or is it better to simply create a whole new installer? I tried following various examples but I keep getting this error: DEBUG: Error 2356 : Couldn't locate cabinet in stream: media1.cab. 回答1: A patch can do anything an updated MSI can do, but it is merely a packaging and delivery mechanism that

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

问题 In base version of my setup, by mistakenly i added the same name for two files like: <component id="x" GUID="guid value"> <file id="x" source="c:\files\x.dll" name="x.dll"> </component> <component id="y" GUID="another guid value"> <file id="y" source="c:\files\y.dll" name="x.dll"> </component> Now I want to change the name to "y.dll" for the file with id="y" using HotFix. If we change the name directly, the compiler error has been thrown "Component "y" has a changed keypath in the transform

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

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