I've seen people pushing MSI building packages which have buttons on UI pages to launch stuff like .NET Framework installers, XNA etc. during the InstallUISequence to bypass this issue. Personally I'd never do this as when a sys admin pushes your package out across their domain your app could install completely fine without those pre-requisites in place but then when their users try to use your app at best it'll fail to run due to missing dependencies (at worst it launches but works in a flawed manner). I'd rather we not have to deal with the support queries which would ensue from that type of situation.
Lisa I'd recommend using something like dotnetinstaller to install your pre-req's before your MSI. It appears to fit your requirements from what you've posted earlier but other bootstrapper packages with similar feature sets may be available (or you could roll your own). See http://dotnetinstaller.codeplex.com/ Palbinder Sandher Software Deployment & IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the <Virtual Environment>** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -----Original Message----- From: Michael Urman [mailto:mur...@gmail.com] Sent: 03 March 2010 13:20 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Nested installation of downloaded prerequisites 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 ------------------------------------------------------------------------------ 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
