The merge module is largely generated automatically - basically the tool that makes the WiX source for the merge module scans an installed JRE and generates one component per folder, there is nothing more to it. There was no concern about supporting any form of minor upgrade. When the WiX code is generated everything gets a new GUID. We only generate new WiX code for the merge module when we migrate to a new version of the JRE. But in the case that is failing it is the very same merge module used by both installers anyway - As I understand it, it is impossible for the module to break the rules on itself. I will try to reproduce the issue and generate logs.
Thanks, Scott On Mon, Sep 21, 2009 at 2:02 PM, Blair <os...@live.com> wrote: > I would be interested in seeing the design of the merge module as well as > install logs. > > With my previous employer we designed and had written much of such a tool > (integrated into our evolving build system). I have plans to write such a > tool, if there is interest I could push it up in the list. > > -----Original Message----- > From: Scott Palmer [mailto:swpal...@gmail.com] > Sent: Monday, September 21, 2009 6:19 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Major Upgrade install - why are files missing? > > Getting back to the original problem. The files that were missing after my > major upgrade install were in a merge module that I created that was the > same in both products and therefore followed the component rules (since > there were no changes to the install path or content of any components). > Would the incorrect scheduling of the RemoveExistingProducts task affect > more than just the VC 2005 redistributables? > It's going to be a tremendous effort to educate all of the people on the > team about the component rules so they can properly update the WiX code for > the installer when they add new files to the project. There doesn't appear > to be any good way to verify that the rules are being followed either. Is > there a tool that can compare my .msi files (V1.msi vs. V2.msi) and warn me > about possible violations to the component rules? I would think that > component guids could be compared between the two msi files and if the > number of files in a component or the install path has changed detailed > warnings could be shown. > > Thanks for your help, > > Scott > > ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
