Thank you, for this great hint. I guess it was my mistake to ignore CustomActions because I did not understand how broad custom actions can be used. I really thought custom actions mean I write custom, error prone code and everything is bad ;-).
Thanks again, Robert On 07.11.2011 22:59, Castro, Edwin G. (Hillsboro) wrote: > The WiX documentation for the CustomAction element already says what the > Error attribute is for: > > http://wix.sourceforge.net/manual-wix3/wix_xsd_customaction.htm > > That page even includes a link to the Custom Action Types page in the Windows > Installer documentation that describes what a type 19 custom action is: > > http://msdn.microsoft.com/library/aa372048.aspx > > "Displays a specified error message and returns failure, terminating the > installation." > > Edwin G. Castro > Software Developer - Staff > Digital Channels > Fiserv > Office: 503-746-0643 > Fax: 503-617-0291 > www.fiserv.com > Please consider the environment before printing this e-mail > >> -----Original Message----- >> From: Robert Brunhuber [mailto:w...@rbrunhuber.de] >> Sent: Monday, November 07, 2011 1:44 PM >> To: wix-users@lists.sourceforge.net >> Subject: Re: [WiX-users] Ensure that a property is set in setup with UI >> orunattended setup. >> >> I'll try this, thank you for your suggestion. Just to understand your example >> shouldn't the InstallExecute Sequence be this way: >> >> <InstallExecute> >> <Custom Action='**CA_BlockPropertyNotSet**' >> After="FindRelatedProducts">NOT PROPERTYTHATMUSTBESET</Custom> >> </InstallExecute> >> >> instead of this: >> >> >> <InstallExecute> >> <Custom Action='BlockPropertyNotSet' After="FindRelatedProducts">NOT >> PROPERTYTHATMUSTBESET</Custom> </InstallExecute> >> >> But I wonder is this request of mine so unusual or why is this not >> documented in >> any way (neither the wix chm nor the book of Nick Ramirez nor any google >> search I could think of)? >> >> Am I doing something wrong? >> >> Thanks, >> >> Robert >> >> On 07.11.2011 22:05, Hoover, Jacob wrote: >>> One would think a simple condition within the InstallExecute table >>> could then trigger a custom action. >>> >>> Ex: >>> <CustomAction Id="CA_BlockPropertyNotSet" >>> Error="!(loc.LaunchCondition_PropertyNotSet)" /> >>> >>> <InstallExecute> >>> <Custom Action='BlockPropertyNotSet' >>> After="FindRelatedProducts">NOT PROPERTYTHATMUSTBESET</Custom> >>> </InstallExecute> >>> >>> -----Original Message----- >>> From: Robert Brunhuber [mailto:w...@rbrunhuber.de] >>> Sent: Monday, November 07, 2011 1:44 PM >>> To:wix-users@lists.sourceforge.net >>> Subject: [WiX-users] Ensure that a property is set in setup with UI >>> orunattended setup. >>> >>> Hi, >>> >>> I have a Wix project, that should create a installer that can be >>> installed either with UI or without UI. So I want to make sure that a >>> property gets set either from the command line or the UI otherwise the >>> installer should abort with a message like "Property PROPRERTYNAME >>> must be set", similar to a launch condition. I searched the web up and >>> down also my searches in the Wix help did not yield anything. >>> >>> I tried to use LaunchCondition but that aborted even before the UI was >>> loaded. >>> >>> Is this possible? If yes, what is the recommended way to do this? >>> I'm using Wix 3.5. >>> >>> Any ideas? >>> >>> Thanks, >>> >>> Robert ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
