Extension libraries
An extension library is a collection of one or more GQI extensions. Every extension is part of such a library. Extensions within the same library are always shipped together, use the same dependencies and can share data.
Extension libraries operate in isolation: extensions that reside in different libraries cannot directly interact which each other.
Tip
When creating multiple GQI extensions that logically belong together, it is good practice to include them in the same extension library.
Working with extension libraries
Each extension library is a standalone DLL file that can be loaded by GQI. The DLL is created by the library compilation feature of the Automation module.
To include multiple extensions in the same library, create them in the same Automation script code block or in the same DIS ad hoc data source project.
See also:
Managing dependencies for GQI extensions
All GQI extensions defined within the same extension library will use the same dependencies.
Similar to Automation scripts, extension libraries may use DLL dependencies that are defined in the DLL references section in the associated Automation script.
From DataMiner 10.5.0 [CU2]/10.5.5 onwards and when using the GQI DxM, GQI also automatically searches for missing dependencies in the C:\Skyline DataMiner\Scripts\Libraries folder. This allows extension scripts to find the necessary Automation script libraries at runtime.
Note
If an Automation script library has its own dependencies, include those dependencies in your GQI extension scripts as well.