nning a msi via a custom action...
Steven,
It sounds like you are calling one MSI from another. This is not a Windows
Installer recommended practice.
If you need to install two MSI's for your application, you should consider
using a bootloader such as Burn to install them one at a time.
Sorry for the false alarm,
Figured it out myself... I had the property named one thing but was calling the
deferred customaction with a different Id than the property name hence it
didn’t work :)
Steve
-Original Message-
From: StevenOgilvie [mailto:sogil...@msn.com]
Sent: September-10
Steven,
It sounds like you are calling one MSI from another. This is not a
Windows Installer recommended practice.
If you need to install two MSI's for your application, you should
consider using a bootloader such as Burn to install them one at a time.
Hope that helps
Chris
-Original
Recursive MSI installs don't work (an oversimplification, but a complete
explanation is too complex). General approaches are to use Burn to install
them separately, or to have one be a prerequisite for the other. This
restriction is why VC Redist runtimes and other MSI-based setups are never
run f
4 matches
Mail list logo
