Hi,
I am developing a custom solution in a DataMiner DaaS environment. I have created a private Class Library (.NET Framework 4.8) to be used by multiple protocols.
However, when I publish my protocol from Visual Studio using DIS, my custom DLL is not being uploaded to the server.
Could you please clarify:
-
What is the official method to include custom assemblies in the deployment package for DaaS?
-
Is there a specific configuration required in the project or
.disfile to ensure these files are synced to theProtocolScriptsfolder? -
What is the recommended folder structure for proprietary libraries in a DaaS instance?
Best regards,
Hi Maximiliano,
When creating a new protocol solution, the solution will have a Dlls folder.
In this folder, you can add any custom DLLs that are used by the connector.
From a QAction project, you can then add a reference to this assembly.
(For more information, refer to Structure of a connector solution.)
When DIS then publishes the connector to the DMA, it will create a dmprotocol package in the background that should include that assembly.
Since you mention that you are creating a class library that will be used by multiple connectors, another option is to publish that library as a NuGet package.
You could then use that NuGet package and DIS will then extract the assembly from the NuGet package when creating the .dmprotocol package. (For more information, refer to Consuming NuGet packages.)