Hi,
my WiX file specifies RemoveExistingProducts as the last action to be
executed. The drawback of this procedure is that when doing an upgrade, there
may be 2 installations in parallel - one that installs the new version and one
that removes the previous one. There's a side effect when using drivers
installations - the upgrade will replace the old driver with the new one and
start the new driver. The old driver is removed, but this does not result in a
removal of the device node from the device tree. That is, when doing an upgrade
with RemoveExistingProducts at the end, the Device Manager will show the
correct version of that particular driver.
It was suggested to me that I should place RemoveExistingProducts after
InstallInitialize action and therefore have uninstallation and installation
serialized.The problem in this case is that the previous drivers are removed,
and the new ones cannot be installed. When the old drivers are installed, the
Device Manager does not refresh the device tree. This means that the new
drivers are installed in the Driver Store and potentially can be installed with
the next reboot. The operating system scans the devices, detects one and if the
drivers are WHQL certified, they will be installed. The operating system will
not install the drivers even if the drivers are signed. The user however can
trigger the drivers installation by selecting Automatic installation on the
"New Hardware Wizard". I would definitely want to bypass this and have the
installer upgrade in a serial fashion.
Best regards,
Calin-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
