Re: [WiX-users] [SPAM] Re: How implement installer to update single file ? Upgrade? Patch?
Question: Can Orca be used to create a transform or patch? I want to update a single DLL. Perhaps this might be an simpler work-around than using Wix? I have tried both approaches Using Patch Creation Properties and Using Purely WiX mentioned on: http://wixtoolset.org/documentation/manual/v3/patching/ They work fine until I try to modify each example to replace the DLL in question. Even then they work up to the point where try to match the original UpgradeCode, ProductId and version codes. Then I get Windows Installer errors saying patch package could not be opened and verify it is a valid Windows installer patch. Thanks in advance for any tips or suggestions, -Ed -Original Message- From: Edward Sutton Sent: Monday, April 28, 2014 2:41 PM To: 'General discussion about the WiX toolset.' Subject: RE: [WiX-users] [SPAM] Re: How implement installer to update single file ? Upgrade? Patch? Are there others experienced in patching/updating that can share an example or offer advice? I followed the Using Patch Creation Properties tutorial which installs an updated sample.txt file. This worked well. http://wixtoolset.org/documentation/manual/v3/patching/patch_building.html Next I copied the working tutorial and started to modify it to do same for updating a DLL instead of the sample.txt file. I have the original 3.8.1 version of the MSI which installs an executable and a DLL. It is only the DLL that I need to replace and not the executable. I suspect my problem may not be setting up matches of the original ids, guids, or references that Orca displays in the original 3.8.1 MSI. 1 - I created a new /3.8.1/product.msi containing the original DLL extracted from the original 3.8.1 version on the MSI. In the product.wxs file I set ProductId and UpgradeCode to match original MSI. 2 - I created a second /3.8.2/product.msi containing the updated DLL. The executable (*.exe) was not changed, only the DLL, so exe was not included. 3 - The patch.msp was created from the patch.wxs from the /3.8.1/product.msi and /3.8.2/product.msi files. My patch has no GUI. When I set my product.wxs ProductId and UpgradeCode to match the original 3.8.1 MSI it launching the patch results in launching of the original installer GUI in repair/remove mode. I tried to do a repair. I confirmed this did *not* update the DLL. I think this is expected when launching original installer. If the patch install would have worked, I expected to see UAC request elevation as it does with the tutorial that installs the pdated sample.txt file. msiexec.exe /p patch\patch.msp /l*vx patch.log Phil it sounds like you are picking this up pretty quickly - I am impressed. I have always struggled with MSI and find it complex. I usually use deployment tools included with Visual Studio, crippled InstallShield versions, Wise Installer, etc. I am trying to take better notes this time as I always have to relearn what I figured out years past. It would like to figure out WiX and start using it with all new projects I have coming up. It sounds like WiX has been around since 2007 and is not likely to disappear. I know I am missing something. Probably multiple things. Any suggestions or patch examples are welcome. -Ed -Original Message- From: Phill Hogland [mailto:phogl...@rimage.com] Sent: Monday, April 28, 2014 1:45 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] [SPAM] Re: How implement installer to update single file ? Upgrade? Patch? While I have not used that process, my understanding is that you are creating a 'small update' patch for the original version of the two MSI files (used in that process). (The updated version of the two MSI files is not distributed. Only the original MSI and the patch which targets only that original MSI.) So in the case where the original MSI is installed and you apply the patch it sounds like it worked. In the case were you tried to apply the patch using a different ProductCode it makes sense that the error message indicated that it could not find the ProductCode indicated on the installed system, as the original MSI did not use that code. I do not have much experience in this area as I am just working through some of these issues myself. So there may be others who can provide better guidance. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-implement-installer-to-update-single-file-Upgrade-Patch-tp7594344p7594388.html Sent from the wix-users mailing list archive at Nabble.com. -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available. Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs
[WiX-users] [SPAM] Re: How implement installer to update single file ? Upgrade? Patch?
While I have not used that process, my understanding is that you are creating a 'small update' patch for the original version of the two MSI files (used in that process). (The updated version of the two MSI files is not distributed. Only the original MSI and the patch which targets only that original MSI.) So in the case where the original MSI is installed and you apply the patch it sounds like it worked. In the case were you tried to apply the patch using a different ProductCode it makes sense that the error message indicated that it could not find the ProductCode indicated on the installed system, as the original MSI did not use that code. I do not have much experience in this area as I am just working through some of these issues myself. So there may be others who can provide better guidance. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-implement-installer-to-update-single-file-Upgrade-Patch-tp7594344p7594388.html Sent from the wix-users mailing list archive at Nabble.com. -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available. Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] [SPAM] Re: How implement installer to update single file ? Upgrade? Patch?
Are there others experienced in patching/updating that can share an example or offer advice? I followed the Using Patch Creation Properties tutorial which installs an updated sample.txt file. This worked well. http://wixtoolset.org/documentation/manual/v3/patching/patch_building.html Next I copied the working tutorial and started to modify it to do same for updating a DLL instead of the sample.txt file. I have the original 3.8.1 version of the MSI which installs an executable and a DLL. It is only the DLL that I need to replace and not the executable. I suspect my problem may not be setting up matches of the original ids, guids, or references that Orca displays in the original 3.8.1 MSI. 1 - I created a new /3.8.1/product.msi containing the original DLL extracted from the original 3.8.1 version on the MSI. In the product.wxs file I set ProductId and UpgradeCode to match original MSI. 2 - I created a second /3.8.2/product.msi containing the updated DLL. The executable (*.exe) was not changed, only the DLL, so exe was not included. 3 - The patch.msp was created from the patch.wxs from the /3.8.1/product.msi and /3.8.2/product.msi files. My patch has no GUI. When I set my product.wxs ProductId and UpgradeCode to match the original 3.8.1 MSI it launching the patch results in launching of the original installer GUI in repair/remove mode. I tried to do a repair. I confirmed this did *not* update the DLL. I think this is expected when launching original installer. If the patch install would have worked, I expected to see UAC request elevation as it does with the tutorial that installs the pdated sample.txt file. msiexec.exe /p patch\patch.msp /l*vx patch.log Phil it sounds like you are picking this up pretty quickly - I am impressed. I have always struggled with MSI and find it complex. I usually use deployment tools included with Visual Studio, crippled InstallShield versions, Wise Installer, etc. I am trying to take better notes this time as I always have to relearn what I figured out years past. It would like to figure out WiX and start using it with all new projects I have coming up. It sounds like WiX has been around since 2007 and is not likely to disappear. I know I am missing something. Probably multiple things. Any suggestions or patch examples are welcome. -Ed -Original Message- From: Phill Hogland [mailto:phogl...@rimage.com] Sent: Monday, April 28, 2014 1:45 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] [SPAM] Re: How implement installer to update single file ? Upgrade? Patch? While I have not used that process, my understanding is that you are creating a 'small update' patch for the original version of the two MSI files (used in that process). (The updated version of the two MSI files is not distributed. Only the original MSI and the patch which targets only that original MSI.) So in the case where the original MSI is installed and you apply the patch it sounds like it worked. In the case were you tried to apply the patch using a different ProductCode it makes sense that the error message indicated that it could not find the ProductCode indicated on the installed system, as the original MSI did not use that code. I do not have much experience in this area as I am just working through some of these issues myself. So there may be others who can provide better guidance. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-implement-installer-to-update-single-file-Upgrade-Patch-tp7594344p7594388.html Sent from the wix-users mailing list archive at Nabble.com. -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available. Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users This email and any files transmitted with it from The Charles Machine Works, Inc. are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error please notify the sender. Our company accepts no liability for the contents of this email, or for the consequences of any actions taken on the basis of the information provided, unless that information is subsequently confirmed in writing. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any