I'm not sure if the email was sent correctly or not. Just resend it.
~~~~~~ Thanks Blair. It's in InstallExecuteSequence. And it's before InstallFinalize. Here's the code: <CustomAction Id="DoDllRegistration" FileKey="FileRegistrator" ExeCommand="/r" Execute="deferred" Return="ignore" HideTarget="no" Impersonate="no" /> <InstallExecuteSequence> <Custom Action="DoDllRegistration" Before="InstallFinalize" >(NOT REMOVE ~= "ALL") AND (&Feature_XYZ = 3)</Custom> </InstallExecuteSequence> Thanks. ________________________________ From: little.forest <little.for...@ymail.com> To: General discussion for Windows Installer XML toolset. <wix-users@lists.sourceforge.net> Sent: Mon, December 13, 2010 3:24:19 PM Subject: Re: [WiX-users] How to write conditions for 'Change' mode Thanks Blair. It's in InstallExecuteSequence. And it's before InstallFinalize. Here's the code: <CustomAction Id="DoDllRegistration" FileKey="FileRegistrator" ExeCommand="/r" Execute="deferred" Return="ignore" HideTarget="no" Impersonate="no" /> <InstallExecuteSequence> <Custom Action="DoDllRegistration" Before="InstallFinalize" >(NOT REMOVE ~= "ALL") AND (&Feature_XYZ = 3)</Custom> </InstallExecuteSequence> Thanks. ________________________________ From: Blair <os...@live.com> To: General discussion for Windows Installer XML toolset. <wix-users@lists.sourceforge.net> Sent: Fri, December 10, 2010 11:57:29 PM Subject: Re: [WiX-users] How to write conditions for 'Change' mode In what sequence is your custom action (execute, or ui)? Where in that sequence is it scheduled (before CostInitialize, after CostFinalize, before or after InstallInitialize, before or after InstallFinalize)? -----Original Message----- From: little.forest [mailto:little.for...@ymail.com] Sent: Friday, December 10, 2010 12:00 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] How to write conditions for 'Change' mode Hi Blair, Thanks for your reply. We'd like to detect whenever the user adds the feature XYZ. Basically, we have a component which is an Outlook plugin. During installation, the user can choose install it or not. If the user doesn't install it in initial install, then she can add it in "Change" mode. There is an old post about this(http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Feature-h ow-to-reinstall-it-or-uninstall-it-alone-td5608464.html#a5608786 ). After enabling the "Change" button, the user can install the feature by hitting the "Change" button. But after that, the dll wasn't registered. From log, I learnt the CA is skipped. So I thought the condition wasn't correct. So I'd like to do the registration CA in "Change" mode, and of course, this happens only if the user really install the component. I thought there is some condition like "(NOT Installed) OR (InstallMode = 'Change')". But there is no such thing. So is this correct? Or there should be some other decent solution? <Custom Action="DoDllRegistration" Before="InstallFinalize" >(NOT REMOVE ~= "ALL") AND (&Feature_XYZ = 3)</Custom> Thanks. ________________________________ From: Blair <os...@live.com> To: General discussion for Windows Installer XML toolset. <wix-users@lists.sourceforge.net> Sent: Fri, December 10, 2010 9:57:26 AM Subject: Re: [WiX-users] How to write conditions for 'Change' mode What are you trying to do in change mode? Detect whenever the user adds Feature_XYZ? Or detect anytime it is either added or stays? It's hard to write conditions when you don't know the scenario. -----Original Message----- From: little.forest [mailto:little.for...@ymail.com] Sent: Thursday, December 09, 2010 10:25 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] How to write conditions for 'Change' mode Hi all, We have a customaction: <Custom Action="DoDllRegistration" Before="InstallFinalize" >(Not Installed) AND (&Feature_XYZ = 3)</Custom> This works in initial install, but not in 'Change' mode. >From here(http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/InstallMo de-Conditions-DON-T-work-td707286.html ), I learnt that "there is no such standard property", and "See "Examples of Conditional Statement Syntax" for how you should do it. " So I googled and found this: http://wix.mindcapers.com/wiki/Conditional_Inner_Text. <!-- Run on initial install, repair and minor upgrade --> <Condition Message='Blah'>COMPANYDIR AND NOT REMOVE ~= "ALL"</Condition> Even if it doesn't say 'Change' mode, I still gave it a try. This statement seems working in 'Change' mode: <Custom Action="DoDllRegistration" Before="InstallFinalize" >(NOT REMOVE ~= "ALL") AND (&Feature_XYZ = 3)</Custom> So the question is, is this the right thing to do? Is there any potential risk that could blow our current stuff? How to write the correct condition for initial install and 'Change' mode? Thanks! ---------------------------------------------------------------------------- -- _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Oracle to DB2 Conversion Guide: Learn learn about native support for PL/SQL, new data types, scalar functions, improved concurrency, built-in packages, OCI, SQL*Plus, data movement tools, best practices and more. http://p.sf.net/sfu/oracle-sfdev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Oracle to DB2 Conversion Guide: Learn learn about native support for PL/SQL, new data types, scalar functions, improved concurrency, built-in packages, OCI, SQL*Plus, data movement tools, best practices and more. http://p.sf.net/sfu/oracle-sfdev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Oracle to DB2 Conversion Guide: Learn learn about native support for PL/SQL, new data types, scalar functions, improved concurrency, built-in packages, OCI, SQL*Plus, data movement tools, best practices and more. http://p.sf.net/sfu/oracle-sfdev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
