hexagon logo

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

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
  • In the earlier VB days, you had to have the Visual Basic runtime-modules installed that handled the VB interpretation in order for your program to "work". Also, the VB created programs were slow compared to C/C++.

    For PC-DMIS specific stuff, pick your preferred weapon of choice, be it VB or whatever. As long as it does what you need it to do, I see no reason to switch to any other language. For me, I picked C# for the variety of supported platforms (I do a lot of other stuff, I tinker and create custom programs to help me (us) in our day-to-day activities). So, I reckoned I'd gain more from going the C# route.

    My personal preference, nothing else.
Reply
  • In the earlier VB days, you had to have the Visual Basic runtime-modules installed that handled the VB interpretation in order for your program to "work". Also, the VB created programs were slow compared to C/C++.

    For PC-DMIS specific stuff, pick your preferred weapon of choice, be it VB or whatever. As long as it does what you need it to do, I see no reason to switch to any other language. For me, I picked C# for the variety of supported platforms (I do a lot of other stuff, I tinker and create custom programs to help me (us) in our day-to-day activities). So, I reckoned I'd gain more from going the C# route.

    My personal preference, nothing else.
Children
No Data