Using WiX 3.11 to create installer that installs different modules that may be uninstalled as a whole

[JETMikeMc]

I have been using a WiX installer project that basically bundles installers from other projects in Visual Studio 2022. I want to change this behavior and have the installer install everything from a single bundle.wxs or product.wxs.

Do I use a or ?

Are each of the "modules" to install encapsulated in a or a ?

I am not an expert WiX by any means, but have put together a bootstrap bundle installer. I want to get away from this so that all of the modules are installed and may be uninstalled as a whole and that the individual parts are not visible in Windows Add/Remove programs.

I must use WiX v3 and not any other installers like InstallShield, etc.

I guess I am not sure of the order of the different WiX sections.

I have tried the following order

....

    <Chain>
        <Fragment>
            .... module 1
        </Fragment>

        <Fragment>
            .... module 2
        </Fragment>

    </Chain>
</Bundle>

I get errors saying the Bundle element contains an unexpected child element 'Fragment'

A Bundle element must have at least one child element of type Chain

[robmen]

You are missing some fundamentals of how WiX works. I'd recommend going through the Tutorial and/or Deployment Dojo. When you have a broader foundation, you'll probably have better luck going forward.

[JETMikeMc]

Robmen, thank you for the information. The tutorial link that you sent me is specific to newer versions of WiX (WiX Toolset v4 and v5 Tutorial). I am on Wix 3.1x and do not plan on (at this time) updating to a newer version. The Deployment Dojo is also specific to newer versions of WiX which does not help me really here.

[robmen]

Contrary to what you've read on the internet, the fundamentals of the WiX Toolset have not changed significantly from v5/v4 to v3.

Oh, there is also the very old v3 tutorial on firegiant.com still. I forget about that because WiX v3 goes out of community service in 3 months and is pretty far in my rearview mirror for non-customers.

[JETMikeMc]

I still am going to stick with WiX 3.11 for now as I don't want to widen the scope and work needed to change existing installers to v5/v4. This I may do for my next version of the project. As for getting an installer to install 3 or 4 separate products in one master installer, I am still looking for a solution. I thought my original post explained the problem.

[robmen]

I thought my original post explained the problem.

It did. Your understanding of how Fragments work is pretty far from how they actually work. That's why I suggested going back to fundamentals.

[JETMikeMc]

Thank Rob. I will look into this. Mike [cid:4b9cb6fc-afc3-4458-a718-1a34f4e6c0ff]

…

________________________________ From: Rob Mensching ***@***.***> Sent: Monday, November 11, 2024 11:04 AM To: wixtoolset/issues ***@***.***> Cc: Mike McWhinney ***@***.***>; Author ***@***.***> Subject: Re: [wixtoolset/issues] Using WiX 3.11 to create installer that installs different modules that may be uninstalled as a whole (Discussion #8821) You don't often get email from ***@***.*** Learn why this is important<https://aka.ms/LearnAboutSenderIdentification> This message was sent from outside the company. Please do not click links or open attachments unless you recognize the source of this email and know the content is safe. I thought my original post explained the problem. It did. Your understanding of how Fragments work is pretty far from how they actually work. That's why I suggested going back to fundamentals. — Reply to this email directly, view it on GitHub<#8821 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BIUOIPNIQMVV22LOG45ZSI32ADPRHAVCNFSM6AAAAABRIYKZ3SVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMRRG4YDKMY>. You are receiving this because you authored the thread.Message ID: ***@***.***>