Is the v1.0.2 patch uninstallable
https://msdn.microsoft.com/en-us/library/aa372102(v=vs.85).aspx ?
If yes you can uninstall it in v1.0.3 by setting MSIPATCHREMOVE
https://msdn.microsoft.com/en-us/library/aa370348%28v=vs.85%29.aspx to
the Patch GUID of v1.0.2 (I haven't tried that but I think
You've set InstallPrivileges to limited in the Package element.
Try omitting it (will default to elevated)
-
Nir Bar
Freelance Developer
Mail: nir@panel-sw.com
Web: www.panel-sw.com
- C++ On Windows, Linux and Embedded Platforms
- WiX InstallShield
--
View this message in
Hi,
I'm currently trying to fix remaining issues in our WiX-based installer.
The current issue I'm trying to fix is WiX/MSI behavior when upgrading an
installation. Upgrading mostly does an uninstallation of the previous
version and installs the new version.
This automatically means that
Is there a way to predict the cache location for my bootstrapper so I can
pass it to my MSI in public property? I need to set a registry value with
the uninstall command for my bootstrapper (similar to the ARP
UninstallCommand) but I'm having a hard time guessing the cache location
for the
Hi All,
Execute setup.exe from MSI package location (which is not packaged) using
MSI.
Step1: Created a c++ custom action to get the current directory and set the
EXEPATH property.
Step2: Set the INSTALLDIR property to setup.exe parent folder path.
Step3: Added a custom action shown below to
Schedule your upgrade late and carefully adhere to the Component Rules.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Tobias Markmann [mailto:tmarkm...@googlemail.com]
Thanks for replying Guys.
@Nir Bar: No it is not possible to have two patches without significant
effort. And also because our updater is not designed that way.
@Mat: Full file patches are too big in size and hence I moved away from
them. Going back to them is not an option.
@Tunney: I've
7 matches
Mail list logo
