It seems Microsoft recommends you use one of the redist executables (vcredist_x86.exe, vcredist_x64.exe) instead of the merge modules (see towards bottom) these days since the 2015 versions of the runtimes are more complicated than before and the merge modules are basically insufficient: “There will not be a merge module for the Universal CRT“. UPDATE: How … Read more
Blank Component GUID: Guid=”” is this something you set recently? This will, I believe, set a blank GUID for the component, meaning that it will be installed on first install and never touched or upgraded afterwards (unless you have found some trick to reinstall the component on upgrade) – and it won’t be uninstalled either … Read more
Newer answers: 1) Companion files, 2) file version hack using Visual Studio, 3) moving the file to another installation path, 4) variations of REINSTALLMODE, 5) “version lying”, etc… All kind of options, most of which are not ideal: File of a new component isn’t installed because there was an old component with the same file … Read more
You could use Product/@Version=”!(bind.FileVersion.FileId)” (replace FileId with the Id of the file from which you’d like to get the version number) and light.exe will populate the value with the version of the file referenced by the FileId. See the WiX v3 documentation for all the available variables.
If you invoke from Powershell, you should use the call operator & This should then also work with parameters enclosed in quotes: & msiexec /i `”My Installer.msi`” /quiet JREPATH=`”c:\BLA BLA`”
Update, Stein Åsmul: Injecting this newer list of cleanup approaches. Find your package in C:\Windows\Installer, where Windows keeps copies of installed MSI packages. The names are generated randomly, so you’ll have to look at the creation dates of the files. Open the MSI file with Orca. (Unfortunately there is no simple download for the orca … Read more
We also encountered this problem where lower-versioned DLLs were not getting reinstalled on a major upgrade. I thought it was strange that the installer would decide which files to install based on the versioning of existing files, then completely uninstall everything, but still only install what what files had been determined to install before uninstalling … Read more
First of all, I would recommend you using PermissionEx instead. It is a standard WiX extension and it has one really huge advantage over Permission – it doesn’t overwrite, but modifies ACLs. And by default, it applies permissions to the folder and all its descendant files and folders, so you don’t have to specify anything … Read more
Faulty Configuration: This line would never run – regardless of silent or interactive mode: <Custom Action=”SilentExecExample” After=”TheActionYouWantItAfter”/> The After attribute must specify a valid StandardAction or CustomAction name. Silent Mode Failure: The line below will fail in silent mode because you run it after InstallFinalize. In this case it will not run with elevation (unless … Read more
This sounded quite mysterious. A quick search found this existing question: Wix string with characters not available in database ‘s codepage although codepage is set. It seems there is a separate code page setting for the MSI’s summary stream – Codepage Summary property – which is different from the package’s main code page setting. I … Read more