J
Jordan
I have an application that needs to be installed in a certain order. It
needs to install the .Net 2.0 runtime, then the application, then some
add-on.
The app that requires the .Net 2.0 support will not install unless it sees
..Net on the computer so it will retry until it can install, however the
add-ons that are supposed to be installed last sometimes install first,
second or third even. I have set which of these three policies should come
first, but that does not seem to garrentee the order of install. What ends
up happening is that the add-ons may get installed before the primary app
and consequently they do not install the support for the primary app because
it has not been detected.
Since the primary app has embeded in it the requirement for .Net support it
will wait until .Net is installed before it installs. Is there a way I can
force the add-on's policy to check for something prior to install?
needs to install the .Net 2.0 runtime, then the application, then some
add-on.
The app that requires the .Net 2.0 support will not install unless it sees
..Net on the computer so it will retry until it can install, however the
add-ons that are supposed to be installed last sometimes install first,
second or third even. I have set which of these three policies should come
first, but that does not seem to garrentee the order of install. What ends
up happening is that the add-ons may get installed before the primary app
and consequently they do not install the support for the primary app because
it has not been detected.
Since the primary app has embeded in it the requirement for .Net support it
will wait until .Net is installed before it installs. Is there a way I can
force the add-on's policy to check for something prior to install?