I have a Suite installer that uses a .NET library to handle Activation Codes to determine which product(s) to install.
In our currently broken implementation we run a pre-requisite installer that puts the library into the GAC and then launches the suite installer. However the standard advice of "Don't run child installs because they don't always work" is holding true and it only works on about half of our test machines.
To get around this I'm wanting to either
a) Have the Suite installer GAC the file prior to running the Activation Code screen. But since the Suite Installer does not manage "Components" that can be deployed into the GAC like I can do w/ an MSI there is not an obvious way to do this. So I need to know how to have the Suite Install GAC a library or...
b) Prior to the dialog asking for the Activation Code place the necessary library in a location ([INSTALLDIR]?) where the installer can access it as if it were in the GAC or on the PATH.
Any insight is greatly appreciated.
Many thanks!
rjsjr
In our currently broken implementation we run a pre-requisite installer that puts the library into the GAC and then launches the suite installer. However the standard advice of "Don't run child installs because they don't always work" is holding true and it only works on about half of our test machines.
To get around this I'm wanting to either
a) Have the Suite installer GAC the file prior to running the Activation Code screen. But since the Suite Installer does not manage "Components" that can be deployed into the GAC like I can do w/ an MSI there is not an obvious way to do this. So I need to know how to have the Suite Install GAC a library or...
b) Prior to the dialog asking for the Activation Code place the necessary library in a location ([INSTALLDIR]?) where the installer can access it as if it were in the GAC or on the PATH.
Any insight is greatly appreciated.
Many thanks!
rjsjr