Thanks for your suggestion Christian.
I followed your adive but looks like my CA is not getting called at all. I
checked the verbose log and there is no entry of my CA.
Following is how I have defined and sequenced my custom action.
SOLUTIONEXISTS = notexists
NOT Installed
NOT In
The condition element is in this context used to show the message and stop
the installation if the condition is false. In other words it is a condition
that must be fulfilled to to start the installation.
The condition you have does the opposite, it shows the message if the DB
doesn't exist. Inste
I am sorry...following is the relavant code snippet. I hope this helps. :)
(declaring properties...)
(defining custom action...)
SOLUTIONEXISTS = exists
(sequencing custom action...)
NOT Installed
NOT Installed
NOT INSTALLED
NOT Installed
CONFIGFILEPATH
1:54:41 AM
Subject: Re: [WiX-users] Condition element not working
My CA is scheduled before AppSearch, since I want to check first if database
exists and accordingly continue or discontinue installation
Code:
SOLUTIONEXISTS = exists
NOT Installed
--
View this message in context:
http://windows
My CA is scheduled before AppSearch, since I want to check first if database
exists and accordingly continue or discontinue installation
Code:
SOLUTIONEXISTS = exists
NOT Installed
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Check-Property
When did you schedule the CA? Hopefully before CostFinalize.
http://msdn.microsoft.com/en-us/library/aa368014(v=vs.85).aspx <-- read the
remarks carefully
---
Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread that deserves
6 matches
Mail list logo
