On 16/01/2013 09:26, Rob Hamflett wrote: > Doesn't this just bring back DLL Hell? It seems that we have to > completely abandon using merge modules for runtime deployment. How is a > user performing a command line installation or repair supposed to know > whether or not it's safe to use the 'a' option for file replacement? > They probably don't know (and have no easy way to find out) whether or > not the installer contains the runtime. It seems like the only safe > option is to copy the runtime DLLs into your application's folder. Sure > you could use the redistributable exe and then link to the system ones, > but given that these could be accidentally downgraded, that's not really > an option. Deploying the DLLs locally doesn't get you any of the > benefits when the shared DLLs are updated, but at least they're less > likely to be downgraded without your knowledge.
Yes, it brings back DLL hell - but isn't the answer not to use 'a' for exactly this reason? -- Bruce Cran ------------------------------------------------------------------------------ Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery and much more. Keep your Java skills current with LearnJavaNow - 200+ hours of step-by-step video tutorials by Java experts. SALE $49.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122612 _______________________________________________ WiX-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wix-users
