Re: [WiX-users] Conditional custom action install

2014-10-09 Thread pezmannen
Thanks, removed the "both" and added condition on this custom action NOT Installed and now repair runs. Although, with Another problem. I'll post it here... Now when my repair works it removes my Application pool account from my Application pool and i can't understand why. Been trying to add con

Re: [WiX-users] Conditional custom action install

2014-10-09 Thread Phill Hogland
I recently implemented a very similar authoring and I do not have any problem doing a Repair. The one difference I noticed is that I am using StartControl/@Remove='uninstall'. I have not tried to set it to 'both' but removing the service while doing an install does not seem to be what I would wan

Re: [WiX-users] conditional custom action

2008-01-22 Thread Christopher Painter
Btw, I'm familiar with the use of "Installed" to make sure you don't create blocking problems for repair and uninstall transactions, but what use is it when coupled with REMOVE="ALL". From what I can see it's not possible to have REMOVE="ALL" without Installed being set. MSI gives the err

Re: [WiX-users] conditional custom action

2008-01-22 Thread Christopher Painter
Note, use of REMOVE="ALL" is only reliable after the InstallValidate action. Richard <[EMAIL PROTECTED]> wrote: In article <[EMAIL PROTECTED]>, "Ted Yu" writes: > > CheckDbExist" BinaryKey="CheckDbExist" /> > > How do I limit the above custom action to be run only at uninstall ? Use the

Re: [WiX-users] conditional custom action

2008-01-22 Thread Richard
In article <[EMAIL PROTECTED]>, "Ted Yu" <[EMAIL PROTECTED]> writes: > > > How do I limit the above custom action to be run only at uninstall ? Use the Condition Installed and REMOVE="ALL" Look at the help page titled "Conditioning Actions to Run During Removal" in the Windows I

Re: [WiX-users] Conditional Custom Action on Install

2007-05-11 Thread Aaron Feng
Thanx Rob, for anyone else that is interested the info can be found here: http://msdn2.microsoft.com/en-us/library/aa368012.aspx Here is the syntax from the doc: (&FeatureName=3) AND NOT(!FeatureName=3) The term "&FeatureName=3" means the action is to install the feature local. The term "NOT(

Re: [WiX-users] Conditional Custom Action on Install

2007-05-10 Thread Rob Mensching
Custom elements can be conditionalized by putting the condition as the text() of the element. The Condition Syntax topic in the MSI SDK has information about how to do what you want. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Aaron Feng Sent: Thursday, May 10, 2007 8:17 PM T