This article provides an overview for how to use the Relative Assembly Path field with plugins.
NOTE: This article applies to DSP® versions 6.5.3 and later. Plugin content is available in DSP help for versions 7.0.3 and later.
Creating a plugin (as in, code that is executed via a DSP event) requires a basic level of C# or Visual Basic .NET development skills. Registering a plugin in the DSP is straightforward. Refer to the Plugins Overview in the online help for full details.
When registering a plugin assembly (as in, a deployment container of one or many plugins), how to populate the Relative Assembly Path is not intuitive; the plugin does not work if this field is not properly populated.
The RELATIVE ASSEMBLY PATH field displays the plugin assembly name relative to the UserArea\[WebAppID]\Processes folder, where
- UserArea is the DSP folder on the application server where all assemblies are stored, and
- WebAppID is the GUID specific to the WebApp.
NOTE: The WebAppID can be found by clicking the Settings menu from any page in the WebApp, then selecting Technical Help. For more information, refer to the Online Help.
How to use the Relative Assembly Path field
If the DLL (i.e., the plugin) is in the Processes folder (on the application server), only enter the assembly name in the Relative Assembly Path field.
Example: With an assembly called “myassembly.dll” located in the Process folder, enter “myassembly.dll” in the Relative Assembly Path field.
If the DLL is in another folder or a sub-folder, enter the assembly name AND the path in the Relative Assembly Path field.
Example: With an assembly called "myassembly.dll" located in a sub-folder in the Processes folder called “bin,” enter "bin\myassembly.dill."