The biggest problem with installing dependencies from your UI sequence is that they do not get called if your MSI is run with silent or basic UI. And then, since your MSI can't show any UI, it's harder for it to explain the failure. One hopes that if a person runs the MSI silently, they know how to capture and interpret a log, however.
On Wed, Mar 3, 2010 at 01:05, Lisa Gracias <lisathelugubri...@gmail.com> wrote: > Would it be alright to call an msi/exe from the UI sequence of another msi, > i.e., before the execute sequence of the parent msi even begins? I've tried > this out and it seems to work. I was wondering if there are any hidden side > effects. > > On Thu, Feb 25, 2010 at 3:37 AM, Sascha Beaumont > <sascha.beaum...@gmail.com>wrote: > >> Unfortunately no. The EXE may contain a compressed MSI anyway :) ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
