VB Exception Thrown by LVclient

[William.Maier]

Hi,

I am trying to use a .dll interop created in LabVIEW for use in VB.  I am trying to use the .dll on a separate machine from the one on which it was created, but the destination machine has LabVIEW Run-time.  However, it seems that the .dll cannot find LabVIEW Run-time.  I am wondering if there is another way I can build the interop or something I can do within VB to make sure the .dll understands where Run-time is.

Image attached showing the VB details for the exception.

Thanks in advance for any help or advice.

-Billy Maier

[tcap]

Hello Billy,

Does the Interop Assembly work on the machine you developed it on?

What versions of LabVIEW, LabVIEW Run-time, Visual Studio, and .NET are you using?

Can you try to make an installer for the Interop Assembly?  This will make sure that the proper version of the LabVIEW Run-time is installed on your target machine. This can be done using the information at the following link:

http://zone.ni.com/reference/en-XX/help/371361H-01/lvhowto/build_installer/

Regards,

[William.Maier]

Yes, it did work on the original machine.

The original machine had LabVIEW 2010 on it.  The destination machine has Visual Studio 2008, version 9.0.30729.1 SP;   .NET version 3.5 SP1; NI Measurement Studio 8.6.35.465; and LabVIEW Run-time 8.6

Unfortunately the nature of this project requires that we cannot install anything further on the destination machine, so we cannot build an installer.

Thanks,

Billy Maier

[Dennis_Knutson]

At http://forums.ni.com/t5/LabVIEW/Problem-with-FGEN-Driver-in-VB/m-p/2997375, you never mentioned that the runtime did not match the version that the interop was developed with. If you can't install a matching version, then why did you even use LabVIEW?

[William.Maier]

The project adviser did not think the lack of matching would be an issue.  He actually was surprised that we even needed Run-time on the machine.  Also, we were developing remotely and unable to see which version was on the machine at the time.

[Dennis_Knutson]

The project adviser has obviously never used LabVIEW. A matching runtime has always been required just like you need the appropriate .NET runtime.

[William.Maier]

He is actually quite skilled with LabVIEW but not very familiar with interfacing it with VB.

[RavensFan]

If he's that familiar with LabVIEW, then he should have been familiar with the concept of a LabVIEW run-time.

[Dennis_Knutson]

The runtime has only been around since version 5.1 or so. The runtime is required for an exe as well as a dll so he's obviously done neither. A quick post here before this ridiculous locking down of your system would have been appropriate.

[William.Maier]

The system was locked down far before I was put on the project.  Not sure why you guys are being so hostile, I thought this forum was supposed to be professional and friendly.  Either way, looks like we'll probably just have to come up with a driver in VB.