Bob Arnson wrote: > It's unlikely to change the date when the bootstrapper becomes > available. Working on it in the v4 branch gives us the flexibility to > ship it in stages and not be "forced" to do a more limited release just > to ship v3. Also note that there's nothing that ties the bootstrapper to > a particular build of WiX; you can easily use v3 to build your setups > and v4 for the bootstrapper.
Fair enough. I'm at the point in my project where I was hoping that I didn't have to build my own bootstrapper. I guess I'll refactor when the bootstrap framework is available. > What aspects of the design are you interested in? The biggest piece is > all internal: e.g., how the worker thread handles installations and > communicates progress with the UX thread. Communicating progress is really one of the things I struggle with. How do you communicate progress with "wrapped" package installations? In other words, if I wanted to bootstrap a prerequisite package that the manufacturer distributes only as an executable setup.exe (not a standalone MSI file)* to provide my user with a unified installation experience, how does your design propose to allow me to do that? *Examples of said packages are the .NET Framework installer and the SQL Server 2005 Express installer. Both are common prerequisites for applications, both are MSI-based installs, but do not provide standalone .MSI installers. Unifying the installation experience for applications that install these packages is difficult-to-impossible. ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
