hexagon logo
Register Sign in
  • Replies 38 replies
  • Subscribers 37 subscribers
  • Views 981 views
  • Users 0 members are here
Options
Related

Got Visual Studio and the Interop.PCDLRN.dll... Now what?

vpt.se
As I upgraded one CMM to Windows 7 64-bit, my small VBS helpers died in the process (still kickin' butt on XP though).
So, I have begun re-coding them in Visual Studio 2010 (I think). I have gotten so far in the coding where I need to connect to PC-DMIS and start interfacing with it. Now, I managed to find the DLL that is supposed to expose some interfaces and methods and I have successfully added it to my project.

Then what? How do I use the DLL to connect to PC-DMIS and expose the PartPrograms collection for instance?

Oh, I am using C# for this...

Any and all input, examples or suggestions are VERY welcome!

TIA!
Parents
  • That's my take on it DaSalo - all I need it for is PC-Dmis related stuff and for that it's easy and works well!


    When I worked for Hex we were contacted by IPI Solutions (who've made VisualFAIR) who were interested in PC-Dmis integration.

    One of their developers (proper C programmer) came to see me, and initially he scoffed (in a nice way) at the fact I was using VB.

    It took me about 5 mins to write a rough script which exported results into excel. He was shocked I could do it so quickly in such a few lines of code. He said it would probably take him about half a day just to hook into excel. No doubt his solution would have been quicker, use less memory and be robust and containing proper error checking and handling etc, but as a tool for COM automation, VB is great!
Reply
  • That's my take on it DaSalo - all I need it for is PC-Dmis related stuff and for that it's easy and works well!


    When I worked for Hex we were contacted by IPI Solutions (who've made VisualFAIR) who were interested in PC-Dmis integration.

    One of their developers (proper C programmer) came to see me, and initially he scoffed (in a nice way) at the fact I was using VB.

    It took me about 5 mins to write a rough script which exported results into excel. He was shocked I could do it so quickly in such a few lines of code. He said it would probably take him about half a day just to hook into excel. No doubt his solution would have been quicker, use less memory and be robust and containing proper error checking and handling etc, but as a tool for COM automation, VB is great!
Children
No Data
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement