...
There are no naming restrictions except that namespaces must be unique between all EngageIP assemblies and all loaded custom code files. The directory structure conventions are located here: https://developer.logisense.com/custom-code-folder-structure-and-naming-conventions/Custom Code Folder Structure and Naming Conventions.
All Custom Code files can implement the optional C# ICustomCodeInstaller interface to perform one time business logic when the custom code is loaded into EngageIP. This interface defines a single method: Install(int ownerID). EngageIP will compile the entire file and execute the Install method when the custom code file is uploaded via the AdminPortal UI. This Install method is where any setup or registration logic should be performed. Some examples are:
...