Re: [WiX-users] Patching and null KeyPath

The component is a service install\remove. We have not set a KeyPath so I guess Wix is choosing one, but looking at the component table in InstEd the KeyPath is null for this component. The machine (A) that is actioning the component I have found has been through a few product upgrades whereas

[WiX-users] How to set string variable in wix burn command line?

Hi, i have given wix burn command like below, bootstrappersetup.exe /i /s install_demodata=0 install_userguide=0 above command is working fine (all are numeric variable), but if i used the below command, bootstrappersetup.exe /i /s install_demodata=0 install_userguide=0 nic2_ipaddress="123.124.12

Re: [WiX-users] Patching and null KeyPath

Need more information. What is the authoring for the component installing the file? What is the actual path to the file in both A and B cases? In the authoring, is the file the KeyPath, or is another file or registry entry the KeyPath? -- John Merryweather Cooper Senior Software Engineer | E

[WiX-users] Patching and null KeyPath

Hello. I'm having an issue with a patch behaving differently on two machine with the same target installation. On one machine (A) the component is action-ed during the patch install and on the other (B) it is not. Other components are behaving the same way, I notice that these all have null Ke

Re: [WiX-users] Updating/Replacing existing MSI with Burn bundle

I have one product that has both x86 and x64 versions. They can be installed side by side. Hence, I have two upgrade codes--one for the x86 and one for the x64. The x64 upgrade only upgrades the x64 side, and the x86 only upgrade the x86. I've been advocating for a bundle-driven install, but

Re: [WiX-users] Updating/Replacing existing MSI with Burn bundle

I have not done exactly what you are doing. (I am converting a large non-msi suite (no UpgradeCode) to a Bundle.exe with an UpgradeCode and many MSI (applications) each with their own UpgradeCodes). However the following blog speaks to your situation: http://www.joyofsetup.com/2008/09/07/hint-be

Re: [WiX-users] Installer for x86 and x64

The statements are pre-compile statements so you would need to build your project twice to get a x64 MSI and a x86 MSI. You can then chain those platform specific packages in a Bundle.exe. I recommend that you look at the following example: http://alekdavis.blogspot.com/2011/05/build-32-and-64-b

Re: [WiX-users] Updating/Replacing existing MSI with Burn bundle

Thank you, Phill. You are right, a major upgrade seems to be the correct approach. I followed the steps of a MajorUpgrade as outlined here (WiX doc) and here (MSDN)

[WiX-users] Missing files after upgrade

Hi, Sometimes after an upgrade there are some binary files missing. It is very strange. Most of the time it works, but after performing the update more than twenty times in a row on a VM, I have some clues. I'm using the mondo UI. If the user chooses default or full, it always works. If he choos

Re: [WiX-users] Uninstall 'Lite' and/or 'Pro' version with RelatedBundle property

Ok I came across the method you prefer to chain several MSI packages. But, what I have now is 2 bundles (let's say Light and Pro) with their own MSI packages. I want the Pro version to uninstall the Light, and vice versa. With RelatedBundle you can detect if they are related but only the version

Re: [WiX-users] Installing x86 after x64 results in Obsolete state

I 'suspect' that the issue is that the x86 MSI package was built first and the x64 built later with a newer version number. So when you try to install the x86 over th x64 it is not allowing you to downgrade the package. My x86 and x64 packages are all exclusive of each other so I have not dealt w

Re: [WiX-users] Uninstall 'Lite' and/or 'Pro' version with RelatedBundle property

You can use Wix XML to author MSI package project(s) or a Bundle (bootstrapper) project, but you do not have to author a bootstrapper. http://wixtoolset.org/documentation/manual/v3/bundle/ A Bundle includes a "Bootstraper Application" (BA) which is processed by the Wix Burn engine. The event hand

Re: [WiX-users] How to use dism.exe in WiX ExePackage for IIS feature activation?

SysWow64 contains 32 bit dism.exe. I know that for some commands to dism.exe in SysWow64 you will get a response of: "You cannot service a running 64-bit operating system with a 32-bit version of DISM. Please use the version of DISM that corresponds to your computer's architecture." Which means

Re: [WiX-users] How to use dism.exe in WiX ExePackage for IIS feature activation?

>>When i make different MSI packages for the different OS- and OS-Bit-versions is it possible to create a MSI package which install no files and just executes the CustomAction? Yes. When there are no files in an MSI you will get ICE71 warnings when building the MSI package. I'm sure there are di

[WiX-users] Uninstall 'Lite' and/or 'Pro' version with RelatedBundle property

Hi, I want to have 2 different installers of a program, let's say lite and pro, like this: http://stackoverflow.com/questions/16429687/how-to-make-a-wix-burn-bundle-that-upgrade-a-lite-version-of-my-product Both have different versions and both have to uninstall each other. Now when I search a

[WiX-users] Message for Install and Uninstall are both be displayed on success page

Hello, I downloaded WiX-Toolset v3.10 and want to have an Install Successful/Uninstall Successful message on Install/Uninstall dialog. Based on this d

Re: [WiX-users] How to use dism.exe in WiX ExePackage for IIS feature activation?

Sorry Phill, i was a little bit misleaded by that answer from Harbinder Singh in Stackoverflow: http://stackoverflow.com/questions/24439602/wix-burn-install-iis-if-not-yet-installed/24491306#24491306 Now i found it out. The ExeCommand of my CustomAction must look like that: One questi

Re: [WiX-users] How to use dism.exe in WiX ExePackage for IIS feature activation?

Thank You Phill, but i now i have a security problem or something like that. I have made a testinstaller, which installs a simple WPF-application with a single mask. In that installer i implemented the customaction like that: [...]