I’m considering adding statsd into my customizations and am looking at the datadog statsdclient.dll. I can add this as a dependency in my C# project(s) and am able to build successfully, but am wondering how this will work in a deployment. Do I need to package the statsdclient.dll with my customization package? Is this supported?
Hi Ben,
The ideal place to add dependent DLLs are the Libs\Business Folder. you can see this folder at the root level during project scaffolding. The cmf cli tool must automatically pick this during the cmf pack command. if you face any issues you can modify the cmfpackage.json to include this dll
I’m coming back to answer my own question. The cmpackage.json file in question will pick up and package all DLLs in the Release directory. So, the key thing is to make sure that any new DLLs (like dogstatsd.dll) and their dependencies are copied into the Release directory. I found that turning on the .NET project’s flag for copying the dependencies to the output dir pulled in way too many additonal DLLs. So, I worked with my AI copilot to determine the minimal set of DLLs and add post build steps to copy just those to the Release directory.