> El 03/11/2014, a las 12:15, Phill Hogland <phogl...@rimage.com> escribió: > > Would it be a better approach to define a wixlib for the 'library' files and > use the wixlib in each msi package which requires the library, so that each > msi package is atomic from msi's perspective? Then on-demand install of > advertised features would be complete.
That would solve the problem with advertising, but then I lose a feature of Burn that is far more important to me: the ability to only download the common libraries if they are not already installed. I'd rather lose auto-repair on launch (why would the files go suddenly missing anyway?). I guess I don't really need advertising, it was just a semi-nice set of behaviors I got for free by just adding Advertise=yes to the shortcut. If it's not going to work properly with the bundles I'm making, I might as well turn them into normal shortcuts... As for on-demand installation of extra features, I'd need a lot more complexity anyway, since the kind of things I'd want to install on demand would need extra downloads. Want to use the Scripting feature -> download and install Python first. As I said in a previous email, we're past the era of small hard disks and physical distribution; installing MSI features on demand from a single large MSI package made far more sense in that scenario (think Office in a CD). -- Nicolás ------------------------------------------------------------------------------ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
