NexusDB

The last step we need to do is to make sure the assembly gets loaded by the server.

Note: If you're using the NexusDB .NET Edition Server, you can skip this step. All you need to do is open the according settings page in the server and load the extension.

For this, look at the Button1Click method we created further up. Uncomment the AddAssembly call, as it will load our assembly, initialize our class and hook it to the monitor. The definition is as follows.

procedure AddAssembly(aClassName: String; anAssemblyName: String; aDebug: InxInterOpDebug = nil);

aClassName is the full namespace and class name for the class to instantiate, in our case NexusDB.Test.nxTestExtender. anAssemblyName is the full path and file name (minus the dll extension) of the library/assembly containing the ChromeExtender class. The last parameter is an optional implementation of the InxInterOpDebug interface. The InterOp pack implementation writes debug messages to a TListbox. Since we want to see some output, we create an instance of this class, and pass it to the function.

Recompile the application, start it, click the button and watch the Win32 NexusDB Server working together with our fully managed .NET class.