2023:Object Library (Node Type): Difference between revisions
Dgreenwood (talk | contribs) |
Dgreenwood (talk | contribs) |
||
| Line 51: | Line 51: | ||
==== Compile the Object Library ==== | ==== Compile the Object Library ==== | ||
{|class="how-to-table" | |||
| | |||
<br> | |||
In order for the '''Object Library''' to work, its code must first be compiled. | In order for the '''Object Library''' to work, its code must first be compiled. | ||
| Line 59: | Line 62: | ||
# Close and re-open Grooper Design Studio. | # Close and re-open Grooper Design Studio. | ||
#* This is an important but sometimes overlooked step. You must close and re-open Grooper Design Studio in order to register the newly compiled DLLs. | #* This is an important but sometimes overlooked step. You must close and re-open Grooper Design Studio in order to register the newly compiled DLLs. | ||
| | |||
[[File:2023 ObjectLibrary 02 02 Compile 01.png]] | |||
|} | |||
[[Category:Articles]] | [[Category:Articles]] | ||
Revision as of 14:36, 6 February 2024
|
STUB |
This article is a stub. It contains minimal information on the topic and should be expanded. |
An Object Library is a .NET framework library containing custom objects used to customize the way Grooper works.
Object Libraries are used to customize Grooper with scripting. They can be used to create a variety of new tools, including custom Activities, custom object commands, custom CMIS Connection types and more.
How To
Import and Compile an Object Library
This tutorial is for users who are attempting to import an Object Library developed by BIS or another Grooper user into their own environment. This will explain how to upload an Object Library to a Project in your environment and compile it.
|
⚠ |
PLEASE NOTE: In version 2023, Object Libraries must be compiled in the Grooper Windows client (thick client), even if they are functional in the web client. |
Import the Grooper ZIP
|
The "Import ZIP Archive" dialog will pop up. |
|
|
|
|
|
|
Compile the Object Library
|
|



