hexagon logo
Register Sign in
  • Replies 19 replies
  • Subscribers 31 subscribers
  • Views 340 views
  • Users 0 members are here
Options
Related

Add Reference to PCDLRN.tlb not working

cduve
Apologies for the duplicate post there was a timeout first time around and I didn't think it was posted! (Can't figure out how to delete it either!)

I'm need to do some VB.Net development on a pc that doesn't have PC-DMIS installed. My understanding is that I need to add a reference to PCDLRN.tlb but when I try that I get the following error:

---------------------------
Microsoft Visual Studio Express 2012 for Windows Desktop
---------------------------
A reference to 'C:\pcdlrn.tlb' could not be added. Please make sure that the file is accessible, and that it is a valid assembly or COM component.

I'm running VSE2012 on Windows 7 64bit. Any ideas what is going on here?

I can add reference to the same file in excel VBA on the pc with PC-DMIS installed without any issues.

Also, where can I get the Object Library reference material? I've seen other post refer to this link but it doesn't work anymore... http://www.wilcoxassoc.com/downloads/dl_documentation.php

Thanks!
Parents
  • I've experienced that issue as well. I believe PCDLRN.Commands (like PCDLRN.PartPrograms and other PC-DMIS "collection" types) does not actually inherit System.Collections. As a result, the Common Language Runtime (the go-between level between VS and the CPU) is unable to compile it in a For...Each...Next (collection-based) loop.

    The PCDLRN.Commands object, while not inheriting System.Collections, does still contain an index property and can be interpreted/compiled by the CLR in a For...Next (index or count-based) loop.

    TL;DR: I think your only choice is to use count-based loops. My theory, FWIW.
Reply
  • I've experienced that issue as well. I believe PCDLRN.Commands (like PCDLRN.PartPrograms and other PC-DMIS "collection" types) does not actually inherit System.Collections. As a result, the Common Language Runtime (the go-between level between VS and the CPU) is unable to compile it in a For...Each...Next (collection-based) loop.

    The PCDLRN.Commands object, while not inheriting System.Collections, does still contain an index property and can be interpreted/compiled by the CLR in a For...Next (index or count-based) loop.

    TL;DR: I think your only choice is to use count-based loops. My theory, FWIW.
Children
No Data
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement