Referencing .Net DLL from an SDK/ EZB Interface

[piraka9011]

Hi,

First time posting here so please let me know if I'm abiding by the guidelines or not.

I am trying to inerface with an EZB JDRevolution robot using LabView 2015 - 32 bit, Windows 7 - 64 bit. The company provided a DLL that runs on the .Net 4.5 framework and 32-bit systems. However, everytime I attempt to create a .Net constructor node and attempt to reference the DLL, I get the error: "An error occred trying to load the assembly."

Whats interesting is that there are other DLLs in the SDK package and I am able to reference those with no problems. Furthermore, a colleague of mine was able to reference the DLL properly, however, when we tried it on our systems, the DLL would not properly reference.

I have tried the 'LabView.exe.config' solution but it did not work (http://digital.ni.com/public.nsf/allkb/567F6EFFC5669C348625739B003739CD).

I have also tried this on a Windows 8.1 Pro - 64 bit system, which did not work, and on LabView 2015 - 64 bit, which obviously also didn't work.

Could this issue be from the SDK? the system? or LabView? Any possible solutions?

Thanks!

[Kyle97330 · Accepted solution]

Is there a chance that there are other DLLs that DLL might reference that aren't in the same directory as it?  That's an additional known cause of that error.

Also just as a FYI that link is broken, it contains the final close parenthesis and period from your sentence. 

[piraka9011]

Whoops, let me edit that. ( http://digital.ni.com/public.nsf/allkb/567F6EFFC5669C348625739B003739CD )

Yes, I forgot to mention that the VI and the DLL are in the same directory. That was one of the troubleshooting steps I tried.

[piraka9011]

Alright, based off @kyle97330's suggestion, I got the solution....Its always the silly things.

The VI was in the same folder as the SDK folder, but not the DLL. Taking all the DLL's out into the exact same folder as the VI made it work.

 Thanks!