You may not have changed the PackageCode - Windows Installer is sensitive to this as well as the ProductCode. --------------- Phil Wilson
On Tue, Apr 8, 2014 at 9:32 AM, Pally Sandher <pally.sand...@iesve.com> wrote: > Unless you also change the Upgrade table when you're poking around in your > MSI with Orca, it's not going to see the "2.0.0.0" as a new package if you > didn't add a MajorUpgrade element when you authored your package. > > See > http://wixtoolset.org/documentation/manual/v3/howtos/updates/major_upgrade.html > > Palbinder Sandher > Software Platform Engineer > T:+44 (0) 141 945 8500 > F:+44 (0) 141 945 8501 > http://www.iesve.com > > **Design, Simulate + Innovate with the <Virtual Environment>** > Integrated Environmental Solutions Limited. Registered in Scotland No. > SC151456 > Registered Office - Helix Building, West Of Scotland Science Park, Glasgow > G20 0SP > Email Disclaimer > > > -----Original Message----- > From: fom Forstner Michael [mailto:f...@keba.com] > Sent: 08 April 2014 09:09 > To: wix-users@lists.sourceforge.net > Subject: [WiX-users] Modify MSI version > > Hello, > > I'm trying to understand how MSI does decide if to use the cached package or > the original package I start from. > Therefore I installed one of my packages with version 1.0.0.0 . After that I > opened the package with Orca and change the product version property to > 2.0.0.0 and gave the product code a new GUID. > > My understanding until now was, that after those changes MSI should consider > the new package as an upgrade while installing it. But it doesn't. > Upon call the logger say's the following: > > [09:44:37:947]: Original package ==> D:\Test.msi > [09:44:37:947]: Package we're running from ==> > C:\Windows\Installer\145ea53f.msi > > The installation then doesn't generate an error but doesn't install the new > version either. Instead it starts only reconfigurating version 1.0.0.0. > > (Counter check: When I install only the modified version 2.0.0.0, the correct > version is registered in the system. So the change itself seems legit) > > Does anyone know why this is? > Do I need to change more? > Is it even possible? > > kind regards, > Michael > > > ------------------------------------------------------------------------------ > Put Bad Developers to Shame > Dominate Development with Jenkins Continuous Integration Continuously > Automate Build, Test & Deployment Start a new project now. Try Jenkins in the > cloud. > http://p.sf.net/sfu/13600_Cloudbees > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > ------------------------------------------------------------------------------ > Put Bad Developers to Shame > Dominate Development with Jenkins Continuous Integration > Continuously Automate Build, Test & Deployment > Start a new project now. Try Jenkins in the cloud. > http://p.sf.net/sfu/13600_Cloudbees > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
