Update: I now know (having actually looked at the schema) that you can use the Sequence attribute of the Custom element to explicitly set the sequence value. Therefore I can sequence all of my custom actions with a value of 1501 (light warns about ICE82), however I do not want to do this without understanding the consequences of using duplicate sequence no's.
Is it simply that you cannot guarantee the order in which they (all CA's with identical sequence) will run? Is so then that's good news as it does not matter in my particular case. I have looked about but found nothing on this, any advice would be most appreciated. From: Stone, Darren Sent: 25 March 2009 15:27 To: [email protected] Subject: [WiX-devs] LGHT0179 and Duplicate Sequence No's in InstallExecuteSequence I am in the process of moving an existing Wix script from version 2.0 to version 3.0. The script in question has a very large number of custom actions scheduled after InstallInitialize, however when running under Wix 3.0 I now get the following error from Light: error LGHT0179 : The InstallExecuteSequence table contains an action 'CA_102' which cannot have a unique sequence number because it is scheduled before or after action 'InstallInitialize'. There is not enough room before or after this action to assign a unique sequence number. Please schedule one of the actions differently so that it will be in a position with more sequence numbers available. Please note that sequence numbers must be an integer in the range 1 - 32767 (inclusive). Having looked into it the problem appears to be that InstallInitialize has a Sequence of 1500 (in InstallExecuteSequence table) and the next standard action (ProcessComponents) has a sequence of 1600. Therefore is I have more than 99 custom actions (my Wix script is auto generated so the CA's are auto sequenced after each other) I get the error above. This didn't happen in version 2.0 as it would blindly continue adding the CA's from sequence 1601 until it reached the next standard action, and so on. Having discovered the above I don't think the Wix 2.0 behaviour was the correct thing to do, but the Wix 3.0 behaviour is causing me a problem. Does anyone have any idea of an elegant (or not) solution to this. Is there a way of using identical sequence no's (i.e. all my CA's sequenced as 1501) and the impact of doing so (I know it's only a Warning from ICE82). Any info on this would be hugely appreciated. ----------------------------------------------------------------------------------------------------- HBOS plc, Registered in Scotland No. SC218813. Registered Office: The Mound, Edinburgh EH1 1YZ. HBOS plc is a holding company, subsidiaries of which are authorised and regulated by the Financial Services Authority. ==============================================================================
------------------------------------------------------------------------------
_______________________________________________ WiX-devs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wix-devs
