InstallAnywhere 2013
Dependencies are components that are needed by the application that is being installed, but are not actually installed by the application’s installer. This is useful if your application relies on other components like an application server or a database that may be installed by other applications. At uninstall time the application will uninstall the component even though it did not install it unless another installed application needs it.
The installer will search the product registry to check if a component with the component ID of the dependency specified is installed. You can also optionally specify a version number or key file location to make the search more specific. You can control when the installer searches for dependencies explicitly by using the Evaluate Dependencies action.
The search will set a series of InstallAnywhere variables based on its findings. The Matched Key File location variable will contain where the dependency is installed. You can use the Dependency State Variable to see if the search was successful. If the dependency check passes the Dependency State Variable will be an empty string. If the dependency check fails the Dependency State Variable will contain the Dependency Failed Message.
For more information about dependencies check out the Sample Dependencies Template that comes with InstallAnywhere. It is sample project that helps illustrate how dependencies work, and what variables are set.
See Also
InstallAnywhere 2013 Help LibraryOctober 2013 |
Copyright Information | Contact Us |