Blair wrote: > First, what was your commandline to pyro? You have to match the @Id of your > PatchBaseline element to the wixmst you supply from torch in your pyro > commandline (e.g. "-t Sample sample.wixmst"). Also your commandline to torch > should include "-p". > > Also, between your baseline and your upgraded you should do the following: > > They have the same values for ProductCode & ProductLanguage. If this is the > only change you may want to consider making ProductVersion identical as > well. In fact, the only difference between the two MSIs (or wixpdbs) should > be that one condition. > > BTW, unless your condition is in the "MainExecutable" component you may want > to try not putting any children in your PatchFamily element. If PatchFamily > is empty it checks everything for inclusion. Otherwise it filters to only > include what is in that list. > Having originally carefully answered the initial bits above, I suspect this may be the problem... The condition isn't part of any component (must remember to read the docs before blindly copying samples), but global in the sense it is part of the product object. Removing the componentRef seemed to have worked - it is now complaining cannot find a file, which is fine as I copied all the object files to a temporary patch directory...
Thanks for your help - I'll let you know I get on John ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) 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/devconference _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
