Bladed Knowledge Base

Creating custom protocols using .NET plugins
Category: Hardware Test module

Problem
Custom protocols do not work as expected.
Solution

When creating a custom protocol using a .NET plugin, please note the following:

GH.Controllers.PluginInterface.dll assembly

- Point no. 1 in Section 11 of the "Bladed Hardware Test User Manual" states that the "GH.Controllers.PluginInterface.dll" assembly should be referenced in the .NET project - this DLL file is located in the "bin" subfolder in the Bladed Hardware Test program folder.

- The "GH.Controllers.PluginInterface.dll" file may also be present in the "Optional PlugIns" subfolder - this version of the file should NOT be referenced by the project or copied into the "PlugIns" subfolder.

Plugin files location

- Point no. 4 in Section 11 of the "Bladed Hardware Test User Manual" states that the compiled plugin DLL and any dependencies should be copied into the "PlugIns" subfolder - although the plugin DLL file itself should be copied into the "PlugIns" subfolder, it is now strongly recommended that any dependencies are placed in the "bin" subfolder (to reduce the risk of performance issues and unintentional conflicts which could occur if dependencies are placed in the "PlugIns" subfolder).





Keywords Hardware test module; BHTM; plug-in; plugin; custom; protocol, controller;