Hi Dojo,
Is there a minimum DataMiner version to take into account when consuming NuGets in a Protocol solution?
According to this post: https://community.dataminer.services/nuget-use-in-system-development/
The NuGet DLL should end up in this folder:
C:\Skyline DataMiner\ProtocolScripts\DllImport\slc.lib.common\1.1.4.2\lib\net462\SLC.Lib.Common.dll
Though, I noticed the DLL ended in the ProtocolScripts folder directly. (I used a DMProtocol package generated by the Jenkins pipeline)
Also after copying the DLL manually into the correct folder, the QAction code still didn't compile well.
Therefor I believe this could be a DM version related issue. The setup where I'm trying out this feature is on: 10.0.0.0-9118
I have now reverted using the NuGet, and I'm using the former Generated Class Library code as workaround for now.
Hi,
I would assume the NuGet class library versions are corresponding with the generated class library versions through DIS.
Meaning that a class library version in the 1.1.x-range will work for a minimum DataMiner version of 9.6.3.0-8092.
And that a class library version in the 1.2.x-range will work for a minimum DataMiner version of 10.0.3.0-8964.
Could you try installing a lower version of the NuGet package that should comply with your DataMiner version?
Hi Robin, Thanks for your reply. I was already aware of the multiple versions. Since I’m building this connector for a DM 10.0.0.0 version, I did use the NuGet for DM 9.6.3 (NuGet v1.1.4.2). The problem really is that the DLL can’t be found it seems…