Hello fellow PC DMIS users,
I don't post here often, but I do visit and read the threads quite frequently. I am looking for help. I have been programming CMM's for about 23 years and have been using PC-DMIS for about 15 of those 23 years. I currently run PC-DMIS 2018 R2 and have been looking to develop my non-PC DMIS related programming skills using Visual Studio. I notice that there are a number of threads going years back that tell how some of you more advanced guru's have been able to interface with PC-DMIS via visual studio.
Now, I am still new to the arena of software development and the majority of object oriented programming I still have yet to understand. My questions are as follows.
Thank you all.
I don't post here often, but I do visit and read the threads quite frequently. I am looking for help. I have been programming CMM's for about 23 years and have been using PC-DMIS for about 15 of those 23 years. I currently run PC-DMIS 2018 R2 and have been looking to develop my non-PC DMIS related programming skills using Visual Studio. I notice that there are a number of threads going years back that tell how some of you more advanced guru's have been able to interface with PC-DMIS via visual studio.
Now, I am still new to the arena of software development and the majority of object oriented programming I still have yet to understand. My questions are as follows.
- Why would anyone find the need to interface with PC-DMIS libraries via Visual Studio since I find most of what I do on a daily basis available in the software already.
- What would be the best choice to interface with PC-DMIS? (i.e. VB.net, Visual C# etc.)
- Do you mostly use console apps to talk to PC-DMIS?
- Having mentioned point in #1, What are some concrete examples of how and why one would use VB.net, or C# etc, in accordance with PC-DMIS.
- Does Hexagon offer any instruction on the where's when's and how's to even begin with this sort of thing?
Thank you all.
Comment