- 26 Sep 2024
- 1 Minute to read
- Print
- DarkLight
SDK: Referencing Third Party Libraries
- Updated on 26 Sep 2024
- 1 Minute to read
- Print
- DarkLight
Overview
Referencing third-party libraries in SDK can be accomplished by referencing .DLL files in a Module, or independently configuring them using File System. Something to note is that .DLL files are referenced in both actions; the difference is where the configuration occurs. This article discusses two ways you can reference .DLL files and provides examples demonstrating the steps necessary to upload them properly.
Referencing .DLL Files within a Module
Users can refer to Building a Module(Advanced) for more information on building a Module in Decisions. Once a module has been created, follow the steps expressed in the article to add a reference to any desired third-party dependencies so they are properly stored in the system.
Additional examples can be accessed by visiting our GitHub Modules.
C:\Program Files\Decisions\Decisions Server\Logs.
Adding Custom .DLL Files with File System
File System can be utilized to add custom .DLL files to your Decision's environment, simply navigate to C:\Program Files\Decisions\Decisions Server\modules\Decisions.Local
If a subfolder for ReferenceDlls
does not exist, create one, and add any desired Third-party libraries inside ReferenceDlls
.
If changes are not seen upon installation, the Decisions Server will need to be restarted. A restart may be required for additional .DLL files uploaded after the initial install.
Please visit Handling Custom .DLL Files for more information on adding custom code to the Decision's platform.