> As far as I can tell, what you have there is a component declaration with a
> condition about whether it should be installed or not.
>
> However the issue seems to be that the custom action ' SchedXmlFile' is being
> called, so what matters is the condition you have on that custom action call,
> in the UI/Execute/event tables, wherever it's called from.
>
> (You may have previously posted that info, but it's been deleted from this
> response.)
>
> Phil Wilson
Thanks for the reply Phil, that makes sense. Here's our defined sequences:
<InstallExecuteSequence>
<Custom Action="PreventDowngrading"
After="FindRelatedProducts">NEWPRODUCTFOUND</Custom>
<Custom Action="PreventOldVersionUpgrading"
After="FindRelatedProducts">OLDPRODUCTFOUND</Custom>
<Custom Action="ConfigureIIs"
After="InstallFiles">&ConfigureIIS6WebSiteFeature=3</Custom>
<!-- Only update Web.config after CopyFile has executed -->
<Custom Action="SchedXmlFile" After="DuplicateFiles"></Custom>
<Custom Action="DbAdminCreateSql" Before="InstallFiles">NOT
UPGRADEFOUND AND NOT USEINTEGRATEDSECURITY</Custom>
<Custom Action="DbAdminCreateWin" Before="InstallFiles">NOT
UPGRADEFOUND AND USEINTEGRATEDSECURITY</Custom>
<Custom Action="DbAdminChange" Before="InstallFiles">UPGRADEFOUND</Custom>
<Custom Action="DatabaseAdminExecute"
Before="InstallFinalize">(&DatabaseSetupFeature=3 OR
&DatabaseUpgradeFeature=3) AND NOT REMOVE</Custom>
<RemoveExistingProducts After="InstallFinalize" />
</InstallExecuteSequence>
<InstallUISequence>
<Custom Action="PreventDowngrading"
After="FindRelatedProducts">NEWPRODUCTFOUND</Custom>
<Custom Action="PreventOldVersionUpgrading"
After="FindRelatedProducts">OLDPRODUCTFOUND</Custom>
</InstallUISequence>
So there is no condition associated with SchedXmlFile.
Of course I then tried setting the SchedXmlFile condition to NOT
UPGRADEFOUND or &DatabaseSetupFeature=3 AND NOT REMOVE, alas,
still no luck.
What's interesting is that now when doing an upgrade the log reports:
Action ended 16:59:58: DuplicateFiles. Return value 1.
MSI (s) (FC:00) [16:59:58:331]: Skipping action: SchedXmlFile
(condition is false)
which is good, but then later in the same log:
Action ended 17:00:21: DuplicateFiles. Return value 1.
MSI (s) (FC:1C) [17:00:21:310]: Doing action: SchedXmlFile
Action 17:00:21: SchedXmlFile.
Action start 17:00:21: SchedXmlFile.
MSI (s) (FC:D8) [17:00:21:316]: Invoking remote custom action. DLL:
C:\Windows\Installer\MSIDFB4.tmp, Entrypoint: SchedXmlFile
MSI (s) (FC!98) [17:00:21:351]: PROPERTY CHANGE: Adding
ExecXmlFileRollback property. Its value is '0C:\Program Files
(x86)\...
MSI (s) (FC!98) [17:00:21:352]: Doing action: ExecXmlFileRollback
Action 17:00:21: ExecXmlFileRollback.
Action start 17:00:21: ExecXmlFileRollback.
ExecXmlFileRollback:
Action ended 17:00:21: ExecXmlFileRollback. Return value 1.
MSI (s) (FC!98) [17:00:21:356]: PROPERTY CHANGE: Adding ExecXmlFile
property. Its value is '10C:\Program Files (x86)\...
MSI (s) (FC!98) [17:00:21:357]: Doing action: ExecXmlFile
Action 17:00:21: ExecXmlFile.
Action start 17:00:21: ExecXmlFile.
ExecXmlFile:
Action ended 17:00:21: ExecXmlFile. Return value 1.
Action ended 17:00:21: SchedXmlFile. Return value 1.
I'm not sure what's going on here, do I need the SchedXmlFile custom
action conditions defined in the other sequences too?
Also, our next upgrade also has to include changes to web.config, so I
will have to call XmlFile for this (major) upgrade.
Thanks,
Simon
------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
