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
  • MS open-sourced .NET Core under the quite permissive MIT license.
    ...


    ... and don't forget the promise not to sue for patent infringement:
    https://github.com/dotnet/corefx/blob/master/PATENTS.TXT

    So, it appears that if you write something that uses the MS .NET core as they provided you're safe and cannot be sued. If you modify the code for .NET then maybe your not so safe (you can be sued for whatever patents they have on .NET ?) which brings up the point of why did they even bother to release the source code if they don't want you to change it?

    I don't trust MS at all. I still remember all the antitrust stuff from around 2000 which showed all of their internal tactics for crushing competitors and squeezing the industry. Even though this is ancient history they still do very questionable things (ISO/IEC 29500 ring a bell, maybe Samba/Kerberos?). Why not just release the code with a GPL license and forget about 'promising' not to sue?

    It doesn't affect me since I don't write anything using .NET and likely never will. I know that many in the free software community distrust MS and it would be amazing if they simply decided to 'jump on board' and start writing .NET components without asking questions about what kind of problems they could run into. If the situation is not absolutely crystal clear when dealing with MS then it is assumed to be a problem (a safe assumption usually). Maybe things are different with MS as compared to what they were back in the early days but this is something they have to demonstrate first. A promise not to sue that disappears if you change the code in .NET doesn't sound too different from how they operated in the past.

    I realize this is way off topic. Sorry for hijacking.
Reply
  • MS open-sourced .NET Core under the quite permissive MIT license.
    ...


    ... and don't forget the promise not to sue for patent infringement:
    https://github.com/dotnet/corefx/blob/master/PATENTS.TXT

    So, it appears that if you write something that uses the MS .NET core as they provided you're safe and cannot be sued. If you modify the code for .NET then maybe your not so safe (you can be sued for whatever patents they have on .NET ?) which brings up the point of why did they even bother to release the source code if they don't want you to change it?

    I don't trust MS at all. I still remember all the antitrust stuff from around 2000 which showed all of their internal tactics for crushing competitors and squeezing the industry. Even though this is ancient history they still do very questionable things (ISO/IEC 29500 ring a bell, maybe Samba/Kerberos?). Why not just release the code with a GPL license and forget about 'promising' not to sue?

    It doesn't affect me since I don't write anything using .NET and likely never will. I know that many in the free software community distrust MS and it would be amazing if they simply decided to 'jump on board' and start writing .NET components without asking questions about what kind of problems they could run into. If the situation is not absolutely crystal clear when dealing with MS then it is assumed to be a problem (a safe assumption usually). Maybe things are different with MS as compared to what they were back in the early days but this is something they have to demonstrate first. A promise not to sue that disappears if you change the code in .NET doesn't sound too different from how they operated in the past.

    I realize this is way off topic. Sorry for hijacking.
Children
No Data