Plugin Assemblies H

Plugin Assemblies (V)

Use this page to Register the Plugin Assembly.

To access this page:

  1. Select Admin > WebApps in the Navigation pane.
  2. Click the Plugins icon for the desired WEBAPP NAME.

 

Plugin Assemblies (V)

Plugin Assemblies (H)

Use this page to Make Changes to a Plugin.

Field

Description

Relative Assembly Path

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. If the DLL is in the Processes folder, only the assembly name displays. If the DLL is in another folder or a sub-folder, the assembly name and the path display. For example, with an assembly called “myassembly.dll” located in the Processes folder, the Relatively Assembly Path displays “myassembly.dll.” However, if that assembly was in a sub-folder called “bin,” the Relative Assembly Path displays “bin\myassembly.dill.”

Assembly Information

Assembly Product

Displays product information for the assembly.

Assembly Title

Displays the name of the container for one or many plugins.

Assembly Description

Displays a description of the assembly.

Assembly Version

Displays the version number of the assembly.

Assembly Culture

Displays the culture that the assembly supports.

Assembly Configuration

Displays the configuration of the assembly; for example, Retail.

Assembly Company

Displays the company name.

Public Key Token

Displays the token that references the public key.

Hosting Environment

Hosting Mode

Displays the hosting state of the plugin.

Options are:

  • InProc – Indicates the plugin is hosted within the current process.
  • InProcCompatible – Indicates the plugin is a legacy style written in an early version of CranSoft.

Cran Soft Permission Set

This field is not used.

Windows Permission Set

This field is not used.

Actions

Update Assembly

Click to repair the assembly. Once it has been repaired, one or more events may still reference the missing plugins. The framework looks at the DLL (assembly) again and checks for any new plugins or changes to the existing plugins.