Hi,
We've updated the NuGet in an automation script to a newer version and saved it as a compiled script in order to be sure that all dependencies will be uploaded to the DataMiner system.
When installing the script via the DataMiner Application Package we can see that everything is uploaded correctly and hitting the validate button results in 0 errors. However, when we try to run the script it throws System.MissingMethodExceptions.
The solution was to restart the SLAutomation process. Since we were using a staging environment this didn't really have an impact. However, we will have to deploy it to production some day and restarting the SLAutomation process in not desired since it could impact other components such as SRM.
Would there be an alternative? Or is this a known issue?
Server version : 10.3.8.0-13183
Client version : 10.3.2325.2012-78ede0fb
Launcher version : 10.3.2324.534-f6dadc78
Thanks in advance.
Kind regards,
After investigation, this is a combination of factors.
First, the NuGet 'A' that was referenced in the Automation script had a dependency on another NuGet package 'X'. However, another version of NuGet 'X' was also referenced in the Automation script. If you expose types from 'X' in NuGet 'A' (e.g. by providing a method that e.g. has as argument a type from 'X', then you can have the mentioned exception if the versions differ. More information can be found here.
Second, the fact that it worked after a DataMiner restart was due to the way default install script is currently implemented. A task has been created to update this behavior: https://collaboration.dataminer.services/task/227329.
Thanks for the intense investigation.