You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using Burn to redistribute my installer and most of the dependencies. That works well, except for one dependency which is packaged using InnoSetup.
The catch here is that while the InstallCommand is just about passing parameters to the source file, to uninstall, I need to run an uninstaller which is installed in the program's Program Files folder.
WiX allows me to specify an UninstallCommand which are arguments passed to the ExePackage during uninstall. In this scenario, I can't run the ExePackage itself but must run a different program.
Support for ExePackages that register in Add/Remove Programs with a value in QuietUninstallString was added in #6772. That should support most Inno based installers.
I'm using Burn to redistribute my installer and most of the dependencies. That works well, except for one dependency which is packaged using InnoSetup.
The catch here is that while the InstallCommand is just about passing parameters to the source file, to uninstall, I need to run an uninstaller which is installed in the program's Program Files folder.
WiX allows me to specify an UninstallCommand which are arguments passed to the ExePackage during uninstall. In this scenario, I can't run the ExePackage itself but must run a different program.
Originally sent by e-mail to wix-dev DL; the consensus then was that this was a feature request http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Uninstalling-an-InnoSetup-based-ExePackage-td7596602.html
The text was updated successfully, but these errors were encountered: