I have discovered the upgrade codes are stored in the following registry location. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UpgradeCodes The registry key name is the upgrade code and the registry key value name is the product code. I can easily extract these values however the codes are stored in a different format. The red circle shows the formatted upgrade code, … Read more
The log file provided shows that newer versions of a few files already on the machine: MSI (s) (0C:5C) [16:13:25:890]: Disallowing installation of component: {015A4DC1-56F4-562B-96B5-B3BE0D45FA5F} since the same component with higher versioned keyfile exists MSI (s) (0C:5C) [16:13:25:890]: Disallowing installation of component: {4B6A1404-3892-5BEF-AB47-8FE3149211A4} since the same component with higher versioned keyfile exists I’ve seen this … Read more
The key thing to know is that there is a BootstrapperCore.dll in the WiX binaries that defines a BootstrapperApplication class that handles the integration with the Burn engine. I needed to create my own derived class and override the ‘Run’ method to launch my custom UI. It was also helpful to use the WixBA project … Read more
The problem is that my custom uninstallation action runs after the removal of standard install files That’s because you have scheduled it before InstallFiles, which comes after RemoveFiles in a standard InstallExecuteSequence. You can also open your MSI file in an editor like Orca or InstEd and have a look at the InstallExecuteSequence table. Sort … Read more
Use one file per component – this avoids all sorts of problems (except .NET assemblies spanning multiple files). See the following thread: One file per component or several files per component? Wix is a great framework for creating installers, but it has a steep learning curve. I strongly recommend you read a few sections of … Read more
The latest supported Visual C++ downloads Runtime Detection Approaches I can find a few ways to detect the presence of the Visual C++ Runtime. Registry Keys used by the VCRedist installer (see section below) Keys mentioned in my original answer – grabbed from this old answer File Presence & Version Check Check for presence of … Read more
Pretty sure you need the product code for this since the upgrade code identifies a family of products, and not a single one. Fire up PowerShell and run this command to get a list of installed products with product code: Get-WmiObject -Class win32_product Here is a different way to get the output in a tabular … Read more
For us, the vast majority of the time was spent invoking light (for the linking phase). light is very slow at compressing cabinets. Changing the DefaultCompressionLevel in the .wixproj from high to mszip (or low or none) helps a lot. However, our build was still too slow. It turns out that light handles cabinets independently, … Read more
I tackled this problem in 3 parts: defining an OSWarningText property which is only set when a warning needs to be given authoring a custom warning screen Inserting the custom warning screen in the UI sequence if necessary 1. Defining an OSWarningText property First, declare the property and give it the “unset” value by default: … Read more
I find the Deployment Tools Foundation project mentioned above to be a solid way to do this from .NET. Having referenced Microsoft.Deployment.WindowsInstaller.dll, use code like this to install a package: Installer.SetInternalUI(InstallUIOptions.Silent); Installer.InstallProduct(msiFilename, “ACTION=INSTALL ALLUSERS=2 MSIINSTALLPERUSER=”); The documentation for the .NET wrapper is in a .chm file in the Windows Installer XML installation directory in Program … Read more