I have to ask again, because I have to make a decision soon. Is there any important point that speaks against modifying the MSI database after build, if it happens in a controlled environment?
As a simple example: --> A MSI package including a property called "configValue=1" --> My tool changes the property in MSI database from "configValue=1" to "configValue=2" Is there some inconsistency going on if I do that, or is it okay? kind regards, Michael -----Ursprüngliche Nachricht----- Von: fom Forstner Michael [mailto:f...@keba.com] Gesendet: Mittwoch, 09. April 2014 13:54 An: General discussion about the WiX toolset. Betreff: Re: [WiX-users] Modify MSI version Hello, I have an additional question concerning that topic. If I consider realizing my installation concept with the possibility to "reconfigure" my MSI packages with my tools, are there any special things I have to consider? These modifications would only go so far that custom properties would be with different values afterwards. No file changes at all. I understand, that if I sign my MSI packages myself after build, that they will get invalidated by changing the MSI database. So I would have to resign it after modification. But is there more? kind regards, Michael -----Ursprüngliche Nachricht----- Von: fom Forstner Michael [mailto:f...@keba.com] Gesendet: Mittwoch, 09. April 2014 10:50 An: General discussion about the WiX toolset. Betreff: Re: [WiX-users] Modify MSI version The PackageCode it was. After updating the SummaryInformation stream via code all works as expected. The background of this question: Because MSI doesn't make use of the fourth version number, I think about making use of it myself to provide minor configuration possibilities to my internal sub-customers without the actual need of writing code. (via a custom written tool). Thanks for your help. kind regards Michael -----Ursprüngliche Nachricht----- Von: Phil Wilson [mailto:phildgwil...@gmail.com] Gesendet: Dienstag, 08. April 2014 19:13 An: General discussion about the WiX toolset. Betreff: Re: [WiX-users] Modify MSI version 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_upg > rade.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 ------------------------------------------------------------------------------ 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 ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/NeoTech _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
