I apologize about the previous post. I didn't trim it down to just minimal text. After this 2nd question, I'll shut up for a while. :)
Hi everyone, In the Wix tutorial, it indicates that (among other things) changing a component ID forces the MSI to be a major upgrade (meaning package GUID, product GUID, and product version have to change). The "What happens if the component rules are broken?" article (http://msdn.microsoft.com/en-us/library/aa372795.aspx) indicates that adding/removing resources to/from a component means the component ID needs to change, forcing a major upgrade. The situation I'm envisioning, I wouldn't want the old and new versions to coexist on the machine. For instance, I have a new dll file that needs to go along with some atomic set of dlls already identified in a component (perhaps I split some work out into its own dll for code maintainability purposes, but they still all install/uninstall together). Thus, it seems I would need to do an uninstall, followed by an install of the new version. If that is true, I need my uninstalls to be non-destructive to data. For example, I don't want to drop a SQL table full of important data that I installed with the old version, just to turn around and recreate it empty in the new version. Should I try to dream up a way to detect its an upgrade and uninstall differently, or is there a best practice that I am missing? Thanks, Jeff Reed | Field Engineering | Duck Creek Technologies | ree...@duckcreektech.com ------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
