There is no reason to be honest. They can end up being in the same MSI in
different features.
I have 2 MSI's now, because after migrating from 3.5 to 6, I decided to use
Burn. This meant removing my Merge Modules (msm A B) (since it's not
recommended anyway).
So I converted them into msi's which was an easy change (MSI A and B).
The MSI which was adding the msm's together in 3.5 is now my bootstrapper,
chaining the MSI's (A and B) together.
I will eventually merge them into 1, in multiple features.. This will not help
with the problem I have though I think... It's going to be more elegant for
sure;)
-Original Message-
From: Nick Ramirez [mailto:nickra...@hotmail.com]
Sent: 21 November 2012 14:41
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Editing files from the Bootstrapper Application
I'm curious about your setup. What is it about it that make having two MSIs
worthwhile? Did you not want to have two Features in a single MSI?
-Original Message-
From: Stelios Kyprou [mailto:stelios.kyp...@fcg.im]
Sent: 21 November 2012 12:34
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Editing files from the Bootstrapper Application
Hi there,
I'm having a Bootsrtapper application, where I have 2 msi's chained. A and B
Msi A represents a codebase, that enables functionality based on a
configuration file.
Msi B depends on A.
In the UI, I am planning to have a screen, where you can select what
functionality you want from the product.
This will decide:
a) What to write to the config file when it is instlled via util:XmlConfig in
MSI A
b) Whether to install MSI B.
What I want is:
When I run the BA again, if I change the desired functionality:
a)Update the config file based on new functionality b)Install/Delete MSI B if
the functionality it provides is wanted/not wanted anymore.
What I am not sure about, is how to approach point (a). When I initially
install, I can provide the values to insert in the config file to MSI A as a
property.
But when I update my selection later on, how should I update this file? Are
Features a good approach? If yes, does this mean I have to reference the same
file in multiple features?
Or do I just do it in code in the BA, without invoking any MSI actions? (Do not
Plan/Apply anything, just do the config edit action).
Thanks in advance
This message w/attachments (message) is intended solely for the use of the
intended recipient(s) and may contain information that is privileged,
confidential or proprietary. If you are not an intended recipient, please
notify the sender, and then please delete and destroy all copies and
attachments, and be advised that any review or dissemination of, or the taking
of any action in reliance on, the information contained in or attached to this
message is prohibited. Formicary cannot guarantee that this message is secure
or free of errors or viruses.
--
Monitor your physical, virtual and cloud infrastructure from a single web
console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud
infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
This message w/attachments (message) is intended solely for the use of the
intended recipient(s) and may contain information that is privileged,
confidential or proprietary. If you are not an intended recipient, please
notify the sender, and then please delete and destroy all copies and
attachments, and be advised that any review or dissemination of, or the taking
of any action in reliance on, the information contained in or attached to this
message is prohibited. Formicary cannot guarantee that this message is secure
or free of errors or viruses.
--
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users