Christopher Painter wrote: > The WiX `philosophy` seems to be don't add .NET dependencies to your > install and don't redist the framework. Just do an AppSearch/Launch > Condition and tell the user to go do it on their own. Personally > this conflicts with my needs and results in one of the many reasons why > I can't use WiX even though I'd like to.
The limitation is with Windows Installer, *not* WiX. The correct way of doing this is either, 1. a bootstrapper that will check for MSI and install it if needed, or 2. just ship your MSI with the requirement condition and let the destination deal with installing .NET 3.5. For corporate deployments, #2 is probably best while option #1 is better for the home user. MSI is just a single-transaction-at-a-time installer. It is not like Debian's APT that can install dozens if not more dependencies for you at the same time as it installs or upgrades hundreds of other applications. - Adam -- Mail Etiquette ============== * Quote properly or not at all. Top posters, this applies to you! * When replying to posts on mailing lists, only address the mailing list unless poster explicitly requested you include them in CC ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
