I don’t have time to test the options I list below, but they should be viable, technical possibilities. Hopefully one of the options will be satisfactory. But, first of all: I dislike this approach of setting secondary, top-level directories – is it really needed? Can you explain the scenario? Maybe there is a more reliable … Read more
INSTALLED should be Installed. Properties are case sensitive and you must definitely fix that in your condition – or else that part of the condition will never be true – even if the product is installed. The rest of the condition looks OK actually. Just some ideas to determine what is wrong: WiX Source Element: … Read more
ProductCode identifies a particular product. It changes every time you ship a new replacement product. UpgradeCode defines a series of products by using the same UpgradeCode in a updated products whose versions are expected to continually increase. By default, new product versions replace older product versions with a major upgrade. Because upgradecode defines a product … Read more
Here’s my two cents…. I don’t find the VersionNT property terribly useful. VersionNT64 is: VersionNT64 …. Not VersionNT64 to determine bitness. This is a bit of a hack (they do this, we do that…) but desperate times call for desperate measures…. In all of the compatibility games MSFT is playing they only seem to be … Read more
Your MSI needs to define a property like so: <Property Id=”SOMEPROPERTY” Value=”Default”/> You can then set this property from the bundle: <MsiPackage SourceFile=”<package>.msi” Id=”SomeId”> <MsiProperty Name=”SOMEPROPERTY” Value=”[SomeProperty]” /> </MsiPackage> After this you can set the property in the Bootstrapper as described here: WiX Bootstrapper: How do I set burn variables from the command line? Notice … Read more
There’s no way to do this without editing the registry, but you can do it programmatically. You have to be sure the icon is included in the deployment. We set our assembly description to the same string as our Product Name, so we can look through the uninstall strings for the right application by searching … Read more
This solved it for me… config file is preserved with minor/major upgrade, and completely removed on uninstall. Ref: Aaron Stebner: How to retain user-customized files during a Windows Installer major upgrade EDIT: Summarized info from the linked page… Each config file shall have it’s own component, where the config file is marked as the keypath … Read more
The wix documentation here explains the Impersonate attribute: This attribute specifies whether the Windows Installer, which executes as LocalSystem, should impersonate the user context of the installing user when executing this custom action. Typically the value should be ‘yes’, except when the custom action needs elevated privileges to apply changes to the machine. You also … Read more
I would simply use one of the already created WiX UI and override the sequence (make it higher so that it will override the previous setting): <Product> … <UI> <UIRef Id=”WixUI_InstallDir” /> <!– Skip license dialog –> <Publish Dialog=”WelcomeDlg” Control=”Next” Event=”NewDialog” Value=”InstallDirDlg” Order=”2″>1</Publish> <Publish Dialog=”InstallDirDlg” Control=”Back” Event=”NewDialog” Value=”WelcomeDlg” Order=”2″>1</Publish> </UI> <Property Id=”WIXUI_INSTALLDIR” Value=”INSTALLFOLDER” /> … … Read more
The WiX tutorial is the #1 resource The people on the mailing list are very helpful There’s a The Code Project article, Creating an installer using Wix v3.0, Votive, and Visual Studio 2005/2008 – Part 2, the GUI that might help Ther’s a bunch of blogs, I keep bumping into Rob Mensching’s (old). Rob Mensching’s … Read more