PlugIns Section
Note
Version 8.0 or later.
In versions prior to 8.0, this section contained a list of file paths specifying the plug-ins to load. Old configuration settings must be migrated to use the new settings specified below.
These settings define the plug-ins for the workstation.
- Parent Sections
- Full Section Key Path Examples
Workstation:PlugIns
| Key | Value Type | Default Value | Description |
|---|---|---|---|
| PackageReferences | collection of PackageReference Section | empty | A collection of package references specifying the plug-ins to be loaded. |
| Directories | collection of strings | empty | A collection of directories from which to load plug-in modules. These directory paths are relative to the Acuit Pinpoint Workstation host computer, even if the settings are defined via the line configuration in Acuit Pinpoint. Paths can include environment variables quoted with the percent sign character (%); these environment variables will be resolved on the Acuit Pinpoint Workstation host computer. Empty items in the collection will be ignored. These settings should normally not be used for regular production stations but can be useful when developing and debugging custom plug-ins. |
Plug-in Packages
Plug-in packages are zip archive files that contain one or more plug-in modules along with any dependencies required by those plug-in modules. Plug-in packages are identified by a package identifier and a version number, where the package file name follows the format {PackageId}.{Version}.zip. For example: MyCompany.MyCustomPlugIn.2.1.0.zip
Acuit Pinpoint Workstation will locate plug-in packages by searching the package sources in the order they are defined in PackageSources. Once a plug-in package is found and retrieved, its files will be extracted to a local directory, and then the plug-in modules within the package will be loaded.