> Also, take a look at http://support.microsoft.com/kb/905238 > > If the assembly version remains the same, but the assembly file version > changes, you will need to schedule RemoveExistingProducts after > InstallIntialize
The linked article contradicts the recommendation above to schedule RemoveExistingProducts after InstallInitialize: Use a Windows Installer table-authoring tool to change the sequencing of the RemoveExistingProducts action in the InstallExecuteSequence table to occur after the InstallFinalize action. For example, use the Orca.exe database table editor for creating or editing Windows Installer packages. After reading the article I understand why it recommends scheduling after InstallFinalize. I do not understand why scheduling after InstallInitialize accomplishes the same result. Can somebody explain? 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 ------------------------------------------------------------------------------ Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
