Split the PI DataLink install kit into 2: PI DataLink (Legacy) and PI DataLink (not legacy)
According to the discussion in the question linked below, PI DataLink (not legacy) uses the PI SDK for loading annotations, even though PI DataLink (not legacy) could use the PI AF SDK for this instead. If PI DataLink (not legacy) was fully migrated to PI AF SDK, then this would leave PI DataLink (Legacy) as the only thing in the PI DataLink install kit that uses PI SDK.
At this point, another improvement can be made: separating PI DataLink (Legacy) and PI DataLink (not legacy) into their own install kits. This way, the main (not legacy) PI DataLink install kit can be decluttered of PI DataLink (Legacy) and PI SDK. Less stuff in the main install kit means that the install kit is smaller and downloads and installs faster on each client computer, and it means that we don't have to wait until PI DataLink (Legacy) is retired to enjoy these benefits.
Please complete the migration of PI DataLink (not legacy) to using PI AF SDK and not PI SDK and then split PI DataLink (Legacy) and PI DataLink (not legacy) into separate install kits.
https://pisquare.osisoft.com/thread/44554-does-pi-datalink-not-legacy-use-pi-sdk
Kenneth Barber
shared this idea
1 comment
-
Kenneth Barber
commented
The link in my post doesn't work anymore. Here is the new link:
https://pisquare.osisoft.com/s/question/0D51I00004ZPqdlSAD/does-pi-datalink-not-legacy-use-pi-sdk