1 of 1 people found this helpful
Have you referenced this white paper discussing custom data references? This talks about the x86/x64 case in the Registering Data References section using regplugin.
Specifically, "If you have built your data reference targeting x86 or x64 platforms instead of AnyCPU. You can have the dlls in separate file locations and register them with RegPlugin by referencing the appropriate paths."
Is there an error you get when trying to register your plugins? What is stopping you from building your plugin for AnyCPU?
Also, building a custom data reference to read data from PHD seems like overkill to me. I think the typical route is to migrate PHD data to PI using OPC methods to move data.
Data References are a type of plug in. As Microsoft designed how plug ins work, be it in Excel, ProcessBook, or even in PI System Explorer, the plug in should not be designed to be 32 bit nor 64 bit, but as AnyCPU. How it will be loaded at runtime depends on the HOSTING application that you are plugging into. PSE 32 bit will load the plug in as 32 bits in its application space. PSE 64 bit will load the exact same plug in as 64 bits in its application space.