[WiX-users] Installing MSI's NOT Included in my Bootstrapper Application Bundle
Greetings, I have a custom C# bootstrapper application that chains a few MSI's together and installs them. No problems here. However, we plan on introducing other add-ons to our software which are not included in our original bootstrapper app chain. These other add-ons will be MSI's (developed by other groups within the company on their own release schedule). Some of these add-ons may be available at the same time we release our main BA. What we would like to do is: * During the installation of our BA we present the user with a screen that allows them to browse for additional add-ons. * These add-ons will be installed through the BA * On uninstall, the original BA chain AND the add-ons should all be removed. What would be the best way to approach this situation? Regards, Robert Ortega -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installing MSI's NOT Included in my Bootstrapper Application Bundle
Related bundles. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: robert_ort...@agilent.com [mailto:robert_ort...@agilent.com] Sent: Wednesday, September 17, 2014 10:44 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Installing MSI's NOT Included in my Bootstrapper Application Bundle Greetings, I have a custom C# bootstrapper application that chains a few MSI's together and installs them. No problems here. However, we plan on introducing other add-ons to our software which are not included in our original bootstrapper app chain. These other add-ons will be MSI's (developed by other groups within the company on their own release schedule). Some of these add-ons may be available at the same time we release our main BA. What we would like to do is: * During the installation of our BA we present the user with a screen that allows them to browse for additional add-ons. * These add-ons will be installed through the BA * On uninstall, the original BA chain AND the add-ons should all be removed. What would be the best way to approach this situation? Regards, Robert Ortega -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installing MSI's NOT Included in my Bootstrapper Application Bundle
Is this still possible even if I do not know what add-ons will be available at the time of my main BA release? It is so difficult finding examples of relatedbundle addons in the archives... Robert -Original Message- From: Rob Mensching [mailto:r...@firegiant.com] Sent: Wednesday, September 17, 2014 10:55 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Installing MSI's NOT Included in my Bootstrapper Application Bundle Related bundles. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: robert_ort...@agilent.com [mailto:robert_ort...@agilent.com] Sent: Wednesday, September 17, 2014 10:44 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Installing MSI's NOT Included in my Bootstrapper Application Bundle Greetings, I have a custom C# bootstrapper application that chains a few MSI's together and installs them. No problems here. However, we plan on introducing other add-ons to our software which are not included in our original bootstrapper app chain. These other add-ons will be MSI's (developed by other groups within the company on their own release schedule). Some of these add-ons may be available at the same time we release our main BA. What we would like to do is: * During the installation of our BA we present the user with a screen that allows them to browse for additional add-ons. * These add-ons will be installed through the BA * On uninstall, the original BA chain AND the add-ons should all be removed. What would be the best way to approach this situation? Regards, Robert Ortega -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installing MSI's NOT Included in my Bootstrapper Application Bundle
I am not an expert and am still learning this topic, but I think it boils
down to:
In the main bundle preemptively add a line like:
RelatedBundle Action='Detect' Id='{GUID to be shared with future related
bundles}' /
In the future add-on, update, or patch, (as indicated) add this to tell it
that it is related to the main product.
RelatedBundle Action='Addon' Id='{GUID in Main bundle ReleatedBundle
elements}' /
I also set Bundle/@Tag to a unique string in each bundle.
I have done limited testing of this approach but it seemed to work so far.
I am interesting in learning it this approach is wrong or incomplete.
There is also info here about code in an mba
http://stackoverflow.com/questions/21612377/schedule-relatedbundle-action-before-primary-bundle
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Installing-MSI-s-NOT-Included-in-my-Bootstrapper-Application-Bundle-tp7596867p7596874.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installing MSI's NOT Included in my Bootstrapper Application Bundle
Thanks Phil. However I'm still not clear about the entire workflow. I only
have one bootstrapper application which includes no addons. Addons will come
later as separate MSI's (on their own physical DVD to make things more
interesting). So on the DVD I'll literally have just one MSI and maybe a text
file readme of some sort.
How do I make the connection between:
RelatedBundle Action='Detect' Id='{GUID to be shared with future related
bundles}' / /**I understand that this is defined in my bootstrapper app**/
And
Addon1.msi (again, this MSI is delivered on a different media and knows nothing
about my bootstrapper app)?
Our initial idea was to have one of our UI screens in our BA prompt for the
media, find the MSI, and install it.
Hope that makes sense..
Regards,
Robert
-Original Message-
From: Phill Hogland [mailto:phogl...@rimage.com]
Sent: Wednesday, September 17, 2014 1:24 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Installing MSI's NOT Included in my Bootstrapper
Application Bundle
I am not an expert and am still learning this topic, but I think it boils down
to:
In the main bundle preemptively add a line like:
RelatedBundle Action='Detect' Id='{GUID to be shared with future related
bundles}' /
In the future add-on, update, or patch, (as indicated) add this to tell it that
it is related to the main product.
RelatedBundle Action='Addon' Id='{GUID in Main bundle ReleatedBundle
elements}' /
I also set Bundle/@Tag to a unique string in each bundle.
I have done limited testing of this approach but it seemed to work so far.
I am interesting in learning it this approach is wrong or incomplete.
There is also info here about code in an mba
http://stackoverflow.com/questions/21612377/schedule-relatedbundle-action-before-primary-bundle
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Installing-MSI-s-NOT-Included-in-my-Bootstrapper-Application-Bundle-tp7596867p7596874.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installing MSI's NOT Included in my Bootstrapper Application Bundle
Rob's advice was to use a Related Bundle , which would involve creating a bundle.exe for each addon, and using the RelatedBundle element in each Bundle to establish the relationships. If you use 'Related Bundles' Burn does a lot of work for you tracking not only the install but the uninstall process. This is a Burn concept and MSI is not going to know about it. I don't know how you would implement your plan. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Installing-MSI-s-NOT-Included-in-my-Bootstrapper-Application-Bundle-tp7596867p7596883.html Sent from the wix-users mailing list archive at Nabble.com. -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installing MSI's NOT Included in my Bootstrapper Application Bundle
Thanks Phil - that tiny piece of information looks to have cleared up most of my confusion. Thanks! -Robert -Original Message- From: Phill Hogland [mailto:phogl...@rimage.com] Sent: Wednesday, September 17, 2014 2:43 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Installing MSI's NOT Included in my Bootstrapper Application Bundle Rob's advice was to use a Related Bundle , which would involve creating a bundle.exe for each addon, and using the RelatedBundle element in each Bundle to establish the relationships. If you use 'Related Bundles' Burn does a lot of work for you tracking not only the install but the uninstall process. This is a Burn concept and MSI is not going to know about it. I don't know how you would implement your plan. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Installing-MSI-s-NOT-Included-in-my-Bootstrapper-Application-Bundle-tp7596867p7596883.html Sent from the wix-users mailing list archive at Nabble.com. -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installing MSI's NOT Included in my Bootstrapper Application Bundle
Could ship a newer bundle that knows about new MSIs and use bundle updates. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: Phill Hogland [mailto:phogl...@rimage.com] Sent: Wednesday, September 17, 2014 2:43 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Installing MSI's NOT Included in my Bootstrapper Application Bundle Rob's advice was to use a Related Bundle , which would involve creating a bundle.exe for each addon, and using the RelatedBundle element in each Bundle to establish the relationships. If you use 'Related Bundles' Burn does a lot of work for you tracking not only the install but the uninstall process. This is a Burn concept and MSI is not going to know about it. I don't know how you would implement your plan. -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
