I have a single installation that installs 2 separate components of our product - either website, windows service (which may reside on a separate server), or both (standalone installation).
I need to install ASP AJAX Extensions 1.0 - but ONLY if the web component feature has been selected. So a prerequisite doesn't work (because then we would ALWAYS require AJAX installation even if not a web installation). I can't assume that clients will have Windows Installer 4.5, nor can that be a requirement or prerequisite - therefore MSI chaining won't work.
I created a custom action with a .Net DLL that checked if it was installed, then kicked off the AJAX MSI if it needed to be installed - but of course I get error 1618 (another MSI installation is already running)...
We had already established that it was a requirement to automatically install the AJAX extensions as part of our installation. It seems that all I am left with is to package the actual DLLs in with my installation and not actually run the installation MSI. This is last resort, and bad form - but do I have any other choices other than to try and kick off a process that waits for the installation to finish before running the AJAX in the background? I don't want to create separate installers for web and service tiers...
FOLLOW US
Get the latest news in Application Packaging