We need to import a 3rd party function library to extend the script functionality of System Platform.
After importing, this library is not recognized by System Platform.
One possibility is that the library does not support the old ".NET Framework", but supports only the new ".NET".
Maybe is something that might be in progress already.
Can you help us or help us find someone who can address this topic?
Thanks!!
Just for clarification, does the import report successfully imported?
Is it imported as script function library or a client control?
I believe your project has to be created under version .Net Framework 2.0 to import.
Is the custom dll developed by you or is it something that you got from a vendor, there could be issues related to dependencies.
Also, to be able to update your dll, make sure to update vendor and version in your build, otherwise it will not overwrite the imported version.
Just for clarification, does the import report successfully imported?
Is it imported as script function library or a client control?
I believe your project has to be created under version .Net Framework 2.0 to import.
Is the custom dll developed by you or is it something that you got from a vendor, there could be issues related to dependencies.
Also, to be able to update your dll, make sure to update vendor and version in your build, otherwise it will not overwrite the imported version.
In addition to this, imported script function library should after import be found in the following locations.
Send me a PM and I will share you the best practices and guide I have from AVEVA, this might assist you in identifying what is happening, but my money is on dependencies.
You should try to verify the SMC log, this should produce a warning if there are missing files.
