[wix-users] Need Advise on Upgrade

[Ven H]

Thanks a lot Edwin for the explanation. However, what I observed was when I
was installing/upgrading the new unbundled MSIs, some files were missing
after installing/upgrading with the new unbundled MSIs. Do I need to
increment the versions of the files (in case of dlls / exes) or change
their binaries every time I want to upgrade, to ensure all files get
installed?


On Sat, Jan 22, 2022 at 12:35 AM Edwin Castro <egcastr at gmail.com> wrote:

> Your new unbundled MSIs should upgrade the MSIs bundled in your
> bootstrapper. I expect that to work normally. Your old bootstrapper will
> still be "installed" and you'll need to tell it to uninstall itself to
> unregister itself. When you do that it will uninstall any bundled MSIs that
> are still installed so you'll want to be careful.
>
> Suppose you have a bundle B that includes MSIs A and C. If you upgrade MSI
> A to MSI A1 but do not also upgrade C to a newer version, then B will be
> installed/registered and C will be installed but MSI A will no longer be
> installed as A1 removed A during upgrade. If you uninstall bundle B now,
> then it will leave MSI A1 installed but will uninstall MSI C. To avoid that
> you'd need to also upgrade MSI C to a newer version. And no matter how you
> go about it, something will need to uninstall bundle B after you've
> upgraded all the new separate MSI.
>
> --
> Edwin G. Castro
>
>
> On Fri, Jan 21, 2022 at 10:20 AM Ven H via wix-users <
> wix-users at lists.wixtoolset.org> wrote:
>
>> Thanks Jim. The bootstrapper will have its own Upgrade and also the MSIs
>> within them will have their own upgrade code. So, when I try to upgrade
>> the
>> Bootstrapper using the individual MSIs, technically it should be treated
>> as
>> an Upgrade itself, right?
>>
>>
>>
>> On Fri, Jan 21, 2022 at 8:23 PM Coryat, Jim via wix-users <
>> wix-users at lists.wixtoolset.org> wrote:
>>
>> > My experience is that you want to target the Upgrade code since that
>> > should be consistent between versions. Also, I have seen the
>> bootstrapper
>> > have a separate ARP entry than that of the actual msi files within the
>> > bootstrapper which made it very confusing.  The msi files would have
>> that
>> > upgrade code within them which would make them a valid target for a
>> > isolated installer (as long as it contained that upgrade code).  We
>> ended
>> > up replacing the bootstrapper with a pure Wix installer that does not
>> rely
>> > on .NET so we can make the .NET framework a component of the install
>> > instead of a prerequisite which necessitated the use of the
>> bootstrapper.
>> > Hope this helps.
>> >
>> > Again, nothing beats creating a test environment and experimenting. 😊
>> >
>> > -----Original Message-----
>> > From: wix-users <wix-users-bounces at lists.wixtoolset.org> On Behalf Of
>> Ven
>> > H via wix-users
>> > Sent: Friday, January 21, 2022 6:38 AM
>> > To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
>> > Cc: Ven H <venh.123 at gmail.com>
>> > Subject: [wix-users] Need Advise on Upgrade
>> >
>> > IMPORTANT NOTICE - This message sourced from an external mail server
>> > outside of the Company.
>> >
>> > We have existing Bootstrapper installers (exe) which bundle
>> Prerequisites
>> > and custom MSIs. These MSIs handle a lot of functionality like Files,
>> > Windows Service Management, IIS Management, Database management etc.
>> Now,
>> > we are planning to break these Bootstrapper installers and separate out
>> > functionality. But there are many customers who have these bootstrappers
>> > installed. Now, when we try to upgrade their system with the separate
>> MSIs,
>> > will it work?
>> >
>> > Bootstrapper has it's own Product & Upgrade code and so also the MSIs.
>> > Also, for majority of the components, the Guid is auto generated. So, on
>> > systems which are installed with the bootstrapper, can I upgrade them
>> with
>> > the separate MSIs? I tried once and observed that the files installed by
>> > bootstrapper seem to be getting removed. Please advise.
>> >
>> > ____________________________________________________________________
>> > WiX Toolset Users Mailing List provided by FireGiant
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.firegiant.com%2F&data=04%7C01%7CJim.Coryat%40softprocorp.com%7C34a75fe7cbb24c208c8608d9dcd290a2%7C8a807b9b02da47f3a903791a42a2285c%7C0%7C0%7C637783619619343905%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=23aTLZYYVUB4iE2LIfyvobki%2BLIeEteSgmlphgHSXs8%3D&reserved=0
>> > ________________________________
>> >  NOTICE: The information contained in this message is proprietary and/or
>> > confidential and may be privileged. If you are not the intended
>> recipient
>> > of this communication, you are hereby notified to: (i) delete the
>> message
>> > and all copies; (ii) do not disclose, distribute or use the message in
>> any
>> > manner; and (iii) notify the sender immediately.
>> >
>> >
>> >
>> > ____________________________________________________________________
>> > WiX Toolset Users Mailing List provided by FireGiant
>> > http://www.firegiant.com/
>>
>> ____________________________________________________________________
>> WiX Toolset Users Mailing List provided by FireGiant
>> http://www.firegiant.com/
>
>