SDK: Referencing Third Party Libraries
- 30 Sep 2024
- 1 Minute to read
- Print
- DarkLight
SDK: Referencing Third Party Libraries
- Updated on 30 Sep 2024
- 1 Minute to read
- Print
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback
Overview
Referencing third-party libraries in SDK can be accomplished by referencing .DLL files in a Module or uploading them into the Decisions portal. 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 store any desired third-party dependencies by adding a reference to them.
Additional examples can be accessed by visiting our GitHub Modules.
Resources for Error Handling
If any issues occur during the process, please refer to
C:\Program Files\Decisions\Decisions Server\Logs. Uploading Custom .DLL Files to the Decisions Portal
Note for Uploading Custom .DLL Files to the Portal
Uploaded Custom .DLL files are project-specific and cannot be used within other projects. Developers who wish to use uploaded .DLL files across different projects must create a Project Dependency between them. Please refer to Project SDK Extensions for more information.
Users can upload custom .DLL files directly into the Decisions portal.
After dragging and dropping your desired file, a menu will appear with the option to import or add the file as a document.
If you receive an error message, please make sure you have chosen the correct folder and re-upload the file.
File(s) that have been uploaded should now be available for use in your project.
.png)
For further information on SDK, visit the Decisions Forum.
Was this article helpful?
