LV8.0 .Net DLL references

[jumpingjack]

I am using Labview 8.0. I have with me 2 .Net C# .dlls. First.dll links uses Second.dll.

I created "Constructor Node" using the First.dll and subsequently a "Invoke Node"  to use a function from the object created. Now the method in "Invoke Node" makes use of the code in the Second.dll. However I am receiving this error message and currently stuck

Error calling method RemoteTestClient.RemoteClient.Connect of ObjectId handle: 0x7E71148 for obj 0x1D0C14E[RemoteTestClient.RemoteClient] in domain [LabVIEW Domain for Run] and thread 2664 >> Exception has been thrown by the target of an invocation. >> Unable to find assembly 'AppFW.Remote, Version=2.60.0.0, Culture=neutral, PublicKeyToken=null'. in CreateRemoteClient.vi

My Vi, First.dll & Second.dll are sitting within the same directory. I had assumed that LV would search the current directory for the required dlls.

Do I need to specify the Second.dll reference manually? If yes, how would I do so.

Thanks,

JJ

[M_B1]

Hi JJ,

I was wondering if you are able to get this to work if you call a function that only uses the first dll, and that does not call the second dll.  Also, can you call a function from the second dll, without it referencing the first dll without this error occurring?

[JonathanN]

Hi JJ,

In addition to Michael's suggestion, I would also verify that you can call your .NET assemblies (and the method you are having issues with) from a simple .NET windows application.  This would isolate the issue to just LabVIEW. You may have already done this but I thought I would throw that out there anyway.

Another thought is that maybe the second assembly isn't getting loaded into memory. To verify this, you could use Process Explorer to look into the LabVIEW.exe process and see if that 2nd assembly is loaded. 

We did fix several issues with regards to .NET in later versions (i.e. 8.2 and 8.2.1) that may be related to your issue but I'm not positive. I would try downloading the evaluation version of LabVIEW 8.2.1 and see if you experience the same problem. This would eliminate any known bugs.

Let me know what you find.

Best Regards,