Hi Mike, Thanks for the info. What you stated is what I am seeing in the verbose logs. I see where the files are being copied, and then I see where they are being removed. Doing a diff between the "good" v1.0.0 case and the "bad" v1.0.0 case makes it obvious.
So if I understand you on the sequencing, I need to configure RemoveExisitingProducts like... <RemoveExistingProducts After="InstallValidate" Before="InstallInitialize"/> or is simply <RemoveExistingProducts After="InstallValidate"/> satisfactory? Will sequencing in this fashion allow a rollback to v1.0.0 to take place if the install of v1.0.1 fails for some reason? One final question. As we create future versions of the product, should I adjust the sequencing of RemoveExistingProducts back to <RemoveExistingProducts After="InstallFinalize"/> since after v1.0.1 all component GUIDs will be generated via the "*" convention? I suppose this could get tricky, as we would need to consider upgrade paths. Thanks!! On Wed, Oct 6, 2010 at 11:06 AM, MikeR <michael.ru...@gmail.com> wrote: > > This is the expected behavior for that configuration. The problem is that > since your component GUIDs don't line up from v1.0.0 to v1.0.1 the upgrade > installs the new components and then after InstallFinalize removes the old > components because it is not able to properly reference count them using > the > component GUIDs. > > You can work around this by sequencing RemoveExistingProducts between > InstallValidate and InstallInitialize. This is a less efficient way of > upgrading as you are basically doing a complete uninstall and reinstall in > one session as opposed to just upgrading the necessary components but it > will solve your current problem. > -- > View this message in context: > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Best-Practices-Using-for-GUID-automation-tp5234716p5607427.html > Sent from the wix-users mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > Beautiful is writing same markup. Internet Explorer 9 supports > standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. > Spend less time writing and rewriting code and more time creating great > experiences on the web. Be a part of the beta today. > http://p.sf.net/sfu/beautyoftheweb > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > ------------------------------------------------------------------------------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
