I have an installer that does an upgrade for every build, part of the
installation is to install a printer.
The custom action that installs the printer has a condition 'NOT Installed'
which is ignored (or not working as I would expect).
Am I correct in thinking that because I am doing an upgrade then the product
is not present as far as MSI is concerned?
Also, would this account for not being able to set the custom action
dependent on a component state as all the components are marked as absent
too?
Or is this because my custom action needs to be placed AFTER CostFinalize?
A snippet of the log file is attached which shows the state of one of the
components (which is already on the system but it looks like the installer
does not recognise this).
MSI (s) (A0:C4) [14:16:23:945]: PROPERTY CHANGE: Deleting
MsiRestartManagerSessionKey property. Its current value is
'452a13078ab7f946a0eb5c0ab5b10b6b'.
MSI (s) (A0:C4) [14:16:23:945]: Feature: DefaultFeature; Installed: Absent;
Request: Local; Action: Local
MSI (s) (A0:C4) [14:16:23:945]: Component: C_SetDefaultPrinter; Installed:
Absent; Request: Local; Action: Local
MSI (s) (A0:C4) [14:16:23:945]: Component: C_InstallPrinter; Installed:
Absent; Request: Local; Action: Local
Regards
Ryan
-------------------------------------------------------------------------
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
