[wix-users] Payload equivalent for MSI

[Fyodor Koryazhkin]

Hi,
There can be other approaches to this problem:
1. If you know exact set of user configurable items then you can read them
from configuration file at the beginning of installation, replace the file
with the one brought with upgrade and then reconfigure it with values read
at the beginning. This approach good if the user configures a few entries
and this set is quite constant.
2. You can include in your installation 2 files: first of them is fully new
file that is used for clean installation and the second contains only
changes (new entries) compared to original one and then during upgrade you
merge them thus keeping user configuration untouched.

Both approaches require writing a bunch of custom code.

On Thu, Jan 19, 2017 at 6:53 PM, Blair Murri <osito at live.com> wrote:

> Immediate actions can easily access the Binary table, but for your
> situation I would also suggest you parse that information into custom
> tables of your own at build time, where your immediately custom actions can
> then incorporate the table data and the on-disk data and make actionable
> determinations that way (reliable, serviceable installations tend to be
> slightly easier that way).
>
> Your immediate actions then simply direct deferred actions to perform
> whatever modifications are required. That separation makes the entire
> system much easier to unit test as well.
>
> Blair Murri
>
> Sent from my Windows 10 phone
>
> From: Griesshammer, Christoph (GE Healthcare)<mailto:christoph.
> griesshammer at ge.com>
> Sent: Wednesday, January 18, 2017 11:54 AM
> To: Blair Murri<mailto:osito at live.com>; wix-users at lists.wixtoolset.org
> <mailto:wix-users at lists.wixtoolset.org>
> Subject: RE: [wix-users] Payload equivalent for MSI
>
> We have two teams working together, one on installation and one on
> serviceability. The serviceability team is using config files and wants to
> keep properties in the config file set on upgrade. But they are also adding
> and removing properties from the config file on upgrades, so we (the
> install team) are essentially doing a merge of the configuration files in
> the package during upgrade.
>
> I know this is the exact reason why you DON'T want to handle configuration
> files during upgrade that can be updated by the user, but we're in this
> boat already, at least for a release, so there's no need to tell me that
> this is the wrong way to handle user configuration and that the application
> should be handling it.
>
> The reason I need to include a "payload" file is because we need to give
> the other team a simple way to indicate some information for the merge. The
> big problem is some properties should always take the user's value from the
> previous version and some properties should take the new default value
> delivered by the config file during an upgrade.
>
> Christoph
>
> From: Blair Murri [mailto:osito at live.com]
> Sent: Wednesday, January 18, 2017 1:56 PM
> To: Griesshammer, Christoph (GE Healthcare) <christoph.griesshammer at ge.com>;
> wix-users at lists.wixtoolset.org
> Subject: EXT: RE: [wix-users] Payload equivalent for MSI
>
>
> The short answer would be the Binary table, but it really depends on how
> and when you're using it, how big it is, and how much effort you're willing
> to expend on maintaining the security of your package.
>
>
>
> Can you describe your use case(s) more?
>
>
>
> Sent from my Windows 10 phone
>
>
>
> From: Griesshammer, Christoph (GE Healthcare)<mailto:christoph.
> griesshammer at ge.com>
> Sent: Wednesday, January 18, 2017 10:50 AM
> To: wix-users at lists.wixtoolset.org<mailto:wix-users at lists.wixtoolset.org>
> Subject: [wix-users] Payload equivalent for MSI
>
>
> Hey folks,
>
> I've been trying to search for the answer but haven't been able to get the
> right language.
>
> What's the payload equivalent in an MSI? I want my installer to deliver a
> file used during installation, but it should be cleaned up before the
> installer is complete.
>
> Thank you,
>
> Christoph Griesshammer
>
>
> ____________________________________________________________________
> WiX Toolset Users Mailing List provided by FireGiant
> http://www.firegiant.com/<https://urldefense.proofpoint.com/
> v2/url?u=http-3A__www.firegiant.com_&d=DQMFAg&c=IV_
> clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=-l6_npd-dx-ekbVSbypvaw-
> IcErQ11UE3f78jQgrCDw&m=RZOcnSFQuH97Bl-cHcjWe1tX7fT_jth9g08AP1q0KCY&s=et0_
> CjehZsKzddxNOVnsJLoiXFCs1QBoWciftdJ4CCU&e=>
>
> ____________________________________________________________________
> WiX Toolset Users Mailing List provided by FireGiant
> http://www.firegiant.com/
>



-- 
Regards,
Fyodor Koryazhkin..