Thanks for the quick response, but I'm a little confused.  Burn has a ton of 
really useful features (flexible and easy to use pre-installation checks, 
downloading or embedding files, etc.) for handling prerequisites and the 
documentation suggests this is one of the main uses for bundles :

"A bundle is a collection of installation packages that are chained together in 
a single user experience. Bundles are often used to install prerequisites, such 
as the .NET Framework or C++ Run Time, before an application's .MSI file. 
Bundles also allow very large applications or suites of applications to be 
broken into smaller, logical installation packages while still presenting a 
single product to the end-user."
 
How would you recommend using bundles for pre-requisites and an application 
with a single .MSI file?  Would the bundle register itself or would it register 
the main application's .MSI file?

It seems very odd for the bundle to be registered since it doesn't have any 
components itself.  For example, I can uninstall all the packages contained in 
the bundle manually and then re-run the bundled setup and it prompts to repair 
or uninstall.

I must be missing something here.

Thanks again,
Dave

------------------------------

Message: 3
Date: Fri, 22 Jun 2012 13:17:38 -0700
From: Rob Mensching <r...@robmensching.com>
Subject: Re: [WiX-users] Using a Bundle for Prerequisites
To: "General discussion for Windows Installer XML toolset."
        <wix-users@lists.sourceforge.net>

As you've found, Burn is not intended to be used this way. The old 
setupexe/setupbld in WiX v3.5 basically does that. I'm sure there are other 
things that do this. Not a lot too it.

Burn solves the problem of creating a unified installation experience across 
many installation packages.


On Fri, Jun 22, 2012 at 12:24 PM, David Mannion <dmann...@transcepta.com>wrote:

> I'm trying to use the Wix Standard Bootstrapper Application to install 
> two system prerequisites before my main application installation, 
> which is already compiled into an Setup.exe.  How can I prevent the 
> bundle from being registered as a separate product.  I am using the 
> DisableModify and DisableRemove attributes, but  this only hides it from 
> Add/Remove programs.
>  Can this be done with by writing a custom Bootstrapper Application?
>
> What I'm really looking for is a way to create a boostrapper that 
> checks if the prerequisiites exist, installs any that are missing, and 
> then launches my setup.exe and gets out of the way.  Can this be done with 
> Burn?
>
> ----------------------------------------------------------------------
> --------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. 
> Discussions will include endpoint security, mobile security and the 
> latest in malware threats. 
> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>



--
virtually, Rob Mensching - http://RobMensching.com LLC


--------------------


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to