Ah, that may be it... they have the same UpgradeCode in the Properties table, but the older version has a completely different code in its Upgrade table, i.e. it's got one code in Properties and another for its table entries. Does this mean I've going to have to do a manual uninstall of the old files?
On Mon, Jul 14, 2014 at 2:26 PM, Phil Wilson <phildgwil...@gmail.com> wrote: > That log has a FindRelatedProducts that finds nothing. In other words > there's no upgrade going on. I would check that the upgrade codes are > identical between this and the intended upgrade target, and that there > are actually entries in the MSI's Upgrade table. If in doubt, check > directly using Orca, checking the Property tables too for UpgradeCode > values. > --------------- > Phil Wilson > > > On Mon, Jul 14, 2014 at 5:11 AM, Sean Duggan <sean.dug...@gmail.com> > wrote: > > I had to get back to work to get the file. The install log comes out to a > > little over 4 MB. That puts it at larger than I can post via Pastebin, > but > > you can access a zipped version at > > > https://drive.google.com/file/d/0B-DeYirjE6WfUGxXYXBLbDFfOEk/edit?usp=sharing > > > > And the very first number in the version changed. It went from 2.0.0.0 to > > 3.0.0.0. > > > > > > > > -----Original Message----- > > Date: Fri, 11 Jul 2014 20:27:29 +0000 > > From: "Hoover, Jacob" <jacob.hoo...@greenheck.com> > > Subject: Re: [WiX-users] What items need to be held in common for a > > major upgrade using MajorUpgrade? > > To: General discussion about the WiX toolset. > > <wix-users@lists.sourceforge.net> > > Message-ID: > > <61d0a1ed0452f744bd7fe991abc2196fdf01a...@exbox2.greenops.com> > > Content-Type: text/plain; charset="us-ascii" > > > > Did anything in the first 3 parts of the version number change? > > > > Also, posting the install log (and linking to it here) would tell us > what > > it's currently doing. > > > > -----Original Message----- > > From: Sean Duggan [mailto:sean.dug...@gmail.com] > > Sent: Friday, July 11, 2014 2:53 PM > > To: wix-users@lists.sourceforge.net > > Subject: [WiX-users] What items need to be held in common for a major > > upgrade using MajorUpgrade? > > > > The company I work with has a utility tool for translating incoming data > in > > the HL7 format into DB operations. We used to support two applications, > > which means our program was named "HL7 for Product X and Product Y". For > > the next release, we're only supporting Product X, so we want to rename > the > > package which gets installed as well as update the DB calls. The person > who > > built the installer also had an incorrect value for the Manufacturer, so > > that will change as well. I set it up as a Major upgrade, using the same > > Update Code GUID for each, because we want the old service to get > > uninstalled. > > > > I attempted to follow the steps in > > > http://wixtoolset.org/documentation/manual/v3/howtos/updates/major_upgrade.html > > and > > http://wix > > . > tramontana.co.hu/tutorial/upgrades-and-modularization/checking-for-oldies, > > but it's not working. The old package is not being removed at all, > > resulting in both of them being present. Is this because the Name and > > Manufacturer were changed? I've tried matching them up, but I'm getting > the > > same result. I'm compiling this using the 3.7 version of the libraries if > > that makes a difference. > > > > FWIW, this is the MajorUpgrade code I'm using: > > <MajorUpgrade > > AllowDowngrades="no" DowngradeErrorMessage="Cannot downgrade > versions." > > AllowSameVersionUpgrades="no" > > /> > > > > > > > > -- > > Sean Duggan sean.dug...@gmail.com > > "*It's easy to win forgiveness for being wrong; being right is what gets > > you into real trouble.*" -Bjarne Stroustrup > > > > -- > > Sean Duggan sean.dug...@gmail.com > > "*It's easy to win forgiveness for being wrong; being right is what gets > > you into real trouble.*" -Bjarne Stroustrup > > > ------------------------------------------------------------------------------ > > Want fast and easy access to all the code in your enterprise? Index and > > search up to 200,000 lines of code with a free copy of Black Duck® > > Code Sight™ - the same software that powers the world's largest code > > search on Ohloh, the Black Duck Open Hub! Try it now. > > http://p.sf.net/sfu/bds > > _______________________________________________ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > ------------------------------------------------------------------------------ > Want fast and easy access to all the code in your enterprise? Index and > search up to 200,000 lines of code with a free copy of Black Duck® > Code Sight™ - the same software that powers the world's largest code > search on Ohloh, the Black Duck Open Hub! Try it now. > http://p.sf.net/sfu/bds > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- Sean Duggan sean.dug...@gmail.com "*It's easy to win forgiveness for being wrong; being right is what gets you into real trouble.*" -Bjarne Stroustrup ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
