Hi
Any idea what is causing the error shown in the snippet? Code worked in VS 2019. Error occurred in VS 2022. Related to PISDKRegistry.dll apparently. Any help appreciated.
good catch! I wasn't sure as the error indicates the exception occurs in PISDKRegistry.dll, indicating the failing component is PI SDK. Might be that Anthony was using the legacy AF SDK which itself is based on PI SDK. The legacy AF SDK is also not included with the recent PI AF Client setup kit and we should only use the Rich Data Access (RDA) flavor of AF SDK with recent projects. I wouldn't assume Visual Studio 2022 creating better executables compared to the compilation results delivered by Visual Studio 2019 but using a recent AF SDK really makes a difference.
Hi Gregor.Beck Just guessing but I would think even the most recent AF SDK still relies upon the unseen but ever-present layer of Managed Data Access (MDA), which takes the PI SDK Component Object Model objects and converts them to managed .NET objects. RDA especially must go throught MDA. Which really means every AF SDK app reading from PI Data Archives still relies upon PI SDK without calling it directly. Just guess again, but I think MDA would include not just fetching recorded values or PI Point objects, but include connection-related stuff since it may convert a PISDK.Server to an AFSDK.PIServer.
Hi Gregor.Beck Just guessing but I would think even the most recent AF SDK still relies upon the unseen but ever-present layer of Managed Data Access (MDA), which takes the PI SDK Component Object Model objects and converts them to managed .NET objects. RDA especially must go throught MDA. Which really means every AF SDK app reading from PI Data Archives still relies upon PI SDK without calling it directly. Just guess again, but I think MDA would include not just fetching recorded values or PI Point objects, but include connection-related stuff since it may convert a PISDK.Server to an AFSDK.PIServer.
