I am trying to create a custom UI for WiX and Burn. I'm almost done except one thing. In the end of installation which is upgrading(for exaple 1.0.0 to 1.1.0) uninstall for the previous version starts and the UI of it shows. My question is how should I handle this so the user doesn't see uninstall UI in the end.
相关问题
- How does the setup bootstrapper detect if prerequi
- Wix: How can I set, at runtime, the text to be dis
- Wix variable name formats with spaces and other ch
- WiX: Multiple MSI files?
- After upgrading to Numpy 1.8.2, ImportError: canno
相关文章
- Handling ffmpeg library interface change when upgr
- chained msi's/Bootstrapper/prerequisite?
- How do I require a value in a textbox in a Wix cus
- How to prevent WiX bundle with same UpgradeCode/Ve
- How do I pass a default 'install location'
- Running msiexec from a service (Local System accou
- Does Java 11 or 12 supports Struts 1.3?
- Can I use msilib or other Python libraries to extr
When performing an upgrade of a Burn-based installer, the process will upgrade each of the MSIs bundled inside the installer, then it will uninstall the previous version's bundle using the commandline arguments
-uninstall -quiet -burn.related.upgrade -burn.embedded
(and a bunch of other stuff). If you're writing a your custom UI in .NET, that will present itself in the WiXBootstrapperApplication
base class with these property values:Command.Action
property asLaunchAction.Uninstall
Command.Display
property ofNone
orEmbedded
When the
Command.Display
is set toNone
orEmbedded
, your custom UI will need to hide itself (ie: don't display a UI). My guess is that you're currently not hiding the UI in this scenario, which is why it's displaying during the upgrade.