We were given a test system with a connector for the AppearTV X20 Platform v2.0.3.1. The problem is that in trying to edit this connector we found that the connector needs Skyline.Dataminer.Utils.ApearTV.X20.API v1.10325.22.0 while the highest published nuget package is 1.0.0.6. Any idea when the newest nuget package will be released so we can more easily modify the connector to our needs?
Hi William,
It looks like the connector has been released with a pre-release version of that NuGet package (only available from the private NuGet store of Skyline). If you want to keep going you can find the package on your DataMiner system after you deploy it. You can find all packages used by DM under the C:\Skyline DataMiner\ProtocolScripts\DllImport folder.
In the meantime, I’ll contact the developers who worked on this connector to see if we can avoid publishing this connector with libraries that are not publicly available.
When making changes to NuGet packages on connectors (or automation scripts), you might need to push these libraries to your DMA (so they are present under the C:Skyline DataMinerProtocolScriptsDllImport folder). To do this, you can use the publish button (available when having the xml file open) in Visual Studio DIS. Or, when having the xml file open you can use File => ‘Save Compiled Protocol As…’ (make sure you use Build => ‘Rebuild Solution’ to ensure all the latest files are compiled) and this way you can save the protocol with the .dmprotocol extension. These .dmprotocol files can be uploaded through Cube from the ‘Protocols & Templates’ app using the ‘Upload…’ button.
Note: Make sure you have the latest DIS version
The dll references Newtonsoft.json 13.0.0.0.0 which doesnt seem to exist in general and further is not resolved properly in the dll according to dotPeek. I tried adding a real version of Newtonsoft.json 13.0.3 via nuget but when trying to load the new protocol I see: (407,32): error CS0234: The type or namespace name ‘Json’ does not exist in the namespace ‘Skyline.DataMiner.Utils’ (are you missing an assembly reference?). Which oddly does not happen in Visual Studio; Only in data miner