Your error messages go in the error table - see the <Error> element. You use the error ID numbers from the error element in the CustomAction element below.
-----Original Message----- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: 23 April 2012 12:54 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Prioritize Launch Conditions You can't set an order for launch conditions. Many people use type 19 custom actions instead. You can control the order in the sequence then. <CustomAction Error="25003" Id="EnsurePrivileged" /> <InstallExecuteSequence> <Custom Action="EnsurePrivileged" Before="AppSearch">not Privileged</Custom> I remember reading on this list that on some OSes, Privileged is always set because you cant know whether the user is going to elevate or not when the install execute sequence starts changing the system state. http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Confusionm-arou nd-Privileged-property-td5945582.html -----Original Message----- From: Ravi Raj [mailto:raviraj.callin...@gmail.com] Sent: 23 April 2012 12:39 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Prioritize Launch Conditions I want to prioritize the launch conditions I am using. I want that first installer checks OS then Admin privilege then DotNet and then component search. I have created this file as below: <?xml version="1.0" encoding="UTF-8"?> <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi";> <Fragment> <Property Id="LaunchConditionsFile" Value="1" /> <Condition Message="!(loc.ValidationAdministrator)">Installed OR Privileged</Condition> <Condition Message="!(loc.ValidationOperatingSystem)"> --condition for OS Check -- </Condition> <Condition Message="!(loc.ValidationDotNetFramework)"> --condition for .NET Check -- </Condition> <PropertyRef Id="R2012" /> <Condition Message="!(loc.ValidationR2012)"> --condition for Component Search Check -- </Condition> </Fragment> </Wix> Now everytime i run the installer, the registry search condition launches first. If I comment this statement then OS check validate comes in picture. How can I overcome this issue? -- Thanks and Regards, Ravi Raj ----------------------------------------------------------------------------- - For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. ----------------------------------------------------------------------------- - For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
