Community Tip - Learn all about PTC Community Badges. Engage with PTC and see how many you can earn! X
have Creo Parametric 7.0.2 Educational version on Win10 with Visual Studio 2019 (16.10.3). I wanted to try VB API and have set-up everything as per vbug - I have registered the COM as admin and the PRO_COMM_MSG_EXE is set as system-level variable to a working path.
When loading VB examples from the installation folder I found that I had to remove pfcls from references and add a fresh reference as per vbug to "Creo Parametric Type Library for Creo Parametric". This new reference was bound as pfc (Interop.pfc in object browser). I changed few imports in the vb examples to replace (string) pfcls with the new reference pfc.
Everything looked well apart from - IpfcAsyncConnection, CCpfcAsyncConnection or anything with word Async is just not included in the COM above. I tried searching for connection method in case AsyncConnection got deprecated but no luck. I also tried referencing the dll manually from Creo 6 on the same machine but I can't see in (com) object browser anything relating to AsyncConnection (ie no interface or class).
Where have IpfcAsyncConnection and related objects gone? Why is it not in the COM?? Do I need a different com or installation? Is this a bug in Creo 7.0.2? Am I doing something wrongly?
I have attached a screenshot from Visual Studio showing reference and compilation error.
Thank you for your help
Solved! Go to Solution.
I found what the issue was - the vb_register_dll didn't register com well (perhaps creo was open at the time or who knows what) so I was inadvertently referencing the *wrong* creo type library. The correct type library is called "Creo VB API Type Library For Creo Parametric..." and I was referencing "Creo Parametric Type Library..." which was wrong.
This was previously resolved here too: https://community.ptc.com/t5/Customization/VB-API-problems/m-p/264429
I found what the issue was - the vb_register_dll didn't register com well (perhaps creo was open at the time or who knows what) so I was inadvertently referencing the *wrong* creo type library. The correct type library is called "Creo VB API Type Library For Creo Parametric..." and I was referencing "Creo Parametric Type Library..." which was wrong.
This was previously resolved here too: https://community.ptc.com/t5/Customization/VB-API-problems/m-p/264429
I found what the issue was - the vb_register_dll didn't register com well (perhaps creo was open at the time or who knows what) so I was inadvertently referencing the *wrong* creo type library. The correct type library is called "Creo VB API Type Library For Creo Parametric..." and I was referencing "Creo Parametric Type Library..." which was wrong.
This was previously resolved here too: https://community.ptc.com/t5/Customization/VB-API-problems/m-p/264429