Hi,
If I leave the default Nuget package references without removing unused ones I get an issue where the DLL references get for example to the following: -
C:\Skyline DataMiner\ProtocolScripts\DllImport\newtonsoft.json\11.0.2\lib\net45\Newtonsoft.Json.dll
C:\Skyline DataMiner\ProtocolScripts\DllImport\sharpziplib\0.86.0\lib\20\ICSharpCode.SharpZipLib.dll
C:\Skyline DataMiner\ProtocolScripts\DllImport\skyline.dataminer.files.interop.sldms\10.1.0.6\lib\net462\Interop.SLDms.dll
C:\Skyline DataMiner\ProtocolScripts\DllImport\skyline.dataminer.files.qactionhelperbaseclasses\10.1.0.6\lib\net462\QActionHelperBaseClasses.dll
C:\Skyline DataMiner\ProtocolScripts\DllImport\skyline.dataminer.files.slmanagedscripting\10.1.0.6\lib\net462\SLManagedScripting.dll
C:\Skyline DataMiner\ProtocolScripts\DllImport\skyline.dataminer.files.protobufnet\10.1.0.6\lib\net462\protobuf-net.dll
C:\Skyline DataMiner\ProtocolScripts\DllImport\skyline.dataminer.files.slprotobuflibrary\10.1.0.6\lib\net462\SLProtoBufLibrary.dll
Clearing unused references resolves this issue from previous solutions I've converted, but I've just got this on a newly created automation script solution that I've moved over to Nuget packages, but not removed unused packages yet.
Hi Philip
Make sure that your projects are migrated to use PackageReference. In the note here you can also see this.
On this page you can also see how to do the migration and how to make VS do it default with PackageReference: What's new in DataMiner Integration Studio v2.39 - DataMiner Dojo
This is quite important as DIS only supports PackageReference. This way it can filter out the DevPacks and their dependencies as those don't need to be included in the dllImport attribute or in the package when publishing.
Thanks Michiel,
I had already migrated to PackageReference, but there was more packages added than needed after that process, which I’ve tidied up, and has resolved the issue.
I’ve also changed PackageReference to the default package management format now.