Feature Requests item #1560183, was opened at 2006-09-17 15:02 Message generated for change (Comment added) made by ferrysoft You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=642717&aid=1560183&group_id=105970
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Priority: 5 Private: No Submitted By: Hilko_Lantinga (hilko_lantinga) Assigned to: Nobody/Anonymous (nobody) Summary: Use RemoveExistingProducts as an attribute of Upgrade Initial Comment: The scheduling of RemoveExistingProducts determines what the upgrade does, so maybe it would be a nice idea to have it as an Upgrade attribute and add a Rollback and RemoveAll attribute). It should have two options, as an example: RemoveExistingProducts="BeforeInstall" and RemoveAll="true" which would schedule between the InstallValidate action and the InstallInitialize action. RemoveExistingProducts="BeforeInstall" and RemoveAll="false" which would schedule after the InstallInitialize action and before any actions that generate execution script. If RemoveExistingProducts="BeforeInstall" then Rollback should not be set. RemoveExistingProducts="AfterInstall" If RemoveExistingProducts="AfterInstall" the Rollback should be selected, as an example: Rollback="RemovePrevious" which would schedule after the InstallFinalize action. Rollback="RemovePreviousInstallNew" which would schedule between the InstallExecute action, or the InstallExecuteAgain action, and the InstallFinalize action. If RemoveExistingProducts="AfterInstall" then RemoveAll should not be set. Rob or Derek should be able to come up with a more logical solution, it could be done with one attributes with 4 values, only picking describing valuenames is hard, maybe mode1 - mode4 is option too. ---------------------------------------------------------------------- Comment By: Mike Green (ferrysoft) Date: 2007-01-08 11:28 Message: Logged In: YES user_id=1108842 Originator: NO I’d like to suggest some alternative naming scheme ideas for this feature request. If a linear naming scheme is required then I suggest the following: RemoveExistingProductsAfter="InstallValidate" RemoveExistingProductsAfter="InstallInitialize" RemoveExistingProductsAfter="InstallExecute" RemoveExistingProductsAfter="InstallFinalize" This does however mean that the documentation for RemoveExistingProducts has to be referred to, in order to choose the right setting. Alternatively, similar documentation describing the meaning of each setting would need to be provided for the Upgrade element. I initially thought that it would be possible to specify which of the four settings was required by using two binary attributes. Unfortunately, the four settings don’t split along binary lines. I suggest the following schemes (in the same order as the scheme above) if binary attributes are required: RemoveOldFirst=”yes” RemoveOldFirst=”no” RollbackOld=”no” RollbackNew=”no” RemoveOldFirst=”no” RollbackOld=”yes” RollbackNew=”yes” RemoveOldFirst=”no” RollbackOld=”yes” RollbackNew=”no” or: UpgradeStrategy=”RemoveOldInstallNew” UpgradeStrategy=”UpgradeOldToNew” RollbackOld=”no” RollbackNew=”no” UpgradeStrategy=”UpgradeOldToNew” RollbackOld=”yes” RollbackNew=”yes” UpgradeStrategy=”UpgradeOldToNew” RollbackOld=”yes” RollbackNew=”no” ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=642717&aid=1560183&group_id=105970 ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ WiX-devs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wix-devs
