It may happen an application uses components, or in another way depends on external factors to function.
Scense’s dependency feature makes it possible to define dependencies between Application objects.
For Example:
A corporate application using an Oracle database, depends on the Oracle client software.
The application object representing the application then must create a dependency to the application object representing the Oracle client.
At the moment the application is started through a shortcut, the Extended Install will make sure the Oracle client is installed first.
Integration in Scense Client.
Scense Client makes it possible to re-install, repair and reset applications depending on their type. If an application has dependencies, these will be taken into account during the re-installation.
The user will be asked whether applications having dependencies with the application to be re-installed should be re-installed as well.
Dependencies and App-V.
Scense will allow dependencies between applications off different types.
If an App-V application is involved in a dependency relation, the dependency behavior will depend on the type of ‘the other’ application.
If an App-V application depends on a Generic-, Windows Installer-, or Virtual Layer application, Scense will make sure such an application is installed before starting the App-V application.
If an App-V application has been made dependent of another App-V application, Scense will create a Dynamic Suite Composition involving the two (or more) App-V applications.
This DSC will be dynamically created on the workstation.
Defining a non App-V application to be dependent of an App-V application may just work because Scense will run the non-App-V application inside the isolated App-V virtual environment. This makes it possible to e.g. make a ThinApp application dependent of an App-V application.
Dependencies and SWV.
Scense will allow dependencies between applications off different types.
If an SWV application is involved in a dependency relation, the dependency behavior will depend on the type of ‘the other’ application.
If an SWV application depends on a Generic- or Windows Installer application, Scense will make sure such an application is installed before starting the SWV application.
If an SWV application has been made dependent of another SWV application, Scense will create SWV Layer Dependencies involving the two (or more) SWV applications.
These Layer Dependencies will be dynamically created on the workstation.
Inter-application type dependencies.
Consider this matrix:
| Main app →
Dependency ↓ |
App-V 5 | App-V 4.x | Windows Installer / Generic | Virtual Layers | ThinApp |
| App-V 5 | Connection Group | App-V 4.x app runs inside App-V 5 bubble | App runs inside App-V 5 bubble | App runs inside App-V 5 bubble | App runs inside App-V 5 bubble |
| App-V 4.x | App-V 5 app runs inside App-V 4.x bubble | Dynamic Suite Composition | App runs inside the App-V 4.x bubble | App runs inside App-V 4.x bubble | App runs inside App-V 4.x bubble |
| Windows Installer / Generic | Access the dependency at OS level | Access the dependency at OS level | Access the dependency at OS level | Access the dependency at OS level | Access the dependency at OS level |
| Virtual Layers | Access the dependency at OS level | Access the dependency at OS level | Access the dependency at OS level | Layer Dependency | Access the dependency at OS level |
| ThinApp | Not supported | Not Supported | Not Supported | Not Supported | Not supported |