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
  • Microsoft is in the process of open-sourcing .NET, for the sole purpose of making it truly cross platform Slight smile

    https://github.com/Microsoft/dotnet

    http://blogs.msdn.com/b/dotnet/


    Cross platform means that your programs can run on any platform unchanged. It doesn't apply to the .NET runtime because this will always be specific to an operating system. The runtime interpreter is what allows your program to work on any supported operating system.

    Microsoft could have released versions of the .NET run time for different operating systems (OS X, GNU/Linux, IOS, ...) but decided to 'open source' it instead. Not sure what this will do. I suspect that most in the free software world are not interested in using .NET anyway due to Microsoft's shifty licenses and probably wouldn't (and likely shouldn't) even look at the source code.

    Also, it is only the core .NET framework. I don't know .NET at all but this sounds like it is bare bones and you wouldn't be able to do much with it anyway. I could be wrong on this point.
Reply
  • Microsoft is in the process of open-sourcing .NET, for the sole purpose of making it truly cross platform Slight smile

    https://github.com/Microsoft/dotnet

    http://blogs.msdn.com/b/dotnet/


    Cross platform means that your programs can run on any platform unchanged. It doesn't apply to the .NET runtime because this will always be specific to an operating system. The runtime interpreter is what allows your program to work on any supported operating system.

    Microsoft could have released versions of the .NET run time for different operating systems (OS X, GNU/Linux, IOS, ...) but decided to 'open source' it instead. Not sure what this will do. I suspect that most in the free software world are not interested in using .NET anyway due to Microsoft's shifty licenses and probably wouldn't (and likely shouldn't) even look at the source code.

    Also, it is only the core .NET framework. I don't know .NET at all but this sounds like it is bare bones and you wouldn't be able to do much with it anyway. I could be wrong on this point.
Children
No Data