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

DaSalo over 9 years ago

VPT.se, your argument seems to be that you are using C# for this because it is good at doing other things. If you are only interested in doing this (writing applications that interact in some way with PCDMIS in a windows environment) what are the advantages to C#? My understanding is that it compiles to essentially the same thing as VB.net in the end so there shouldn't be a big performance advantage. Are there really useful libraries out there that this allows you to take advantage of or really efficient methods for handling vector arrays?

Cappy, perhaps you can comment on this?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
cappy6124 over 5 years ago in reply to DaSalo

IMO C# > VB.NET. yes it gets compiled the same, but there are certain aspects of C# that don't exist in VB.NET. LINQ for example is a huge time saver. I also never really liked the syntax of vb.net. C# is much closer to C/C++
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Reply

cappy6124 over 5 years ago in reply to DaSalo

IMO C# > VB.NET. yes it gets compiled the same, but there are certain aspects of C# that don't exist in VB.NET. LINQ for example is a huge time saver. I also never really liked the syntax of vb.net. C# is much closer to C/C++
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Children

No Data