03-02-2011 01:08 PM
Have you solved this problem, smittywood?
I see this error in 2 common cases:
1: A 32 bit LabVIEW built assembly is called from a 64 bit Visual Studio build.
The solution here is to force Visual Studio build to be targeted for x86.
2: The built Visual Studio image (executable) references a dependency (managed and not in GAC or unmanaged) of the assembly that cannot be found by Windows (not in system32 or in the host process executable's folder) when executed.
The solution to this is to ensure those dependencies can be found. These dependencies are copied to a support folder next to the built assembly by LabVIEW, so you can look here to see if there are dependencies that need to be added as references to be copied to the build directory in your Visual Studio project.
Evan Prothro
RF Systems Engineer | NI
03-02-2011 01:12 PM
NI helped me with the resolution. The problem turned out to be I was building the interop assembly in the instr.lib folder. When I changed the destination directory to be outside the instr.lib folder it worked fine.
Thanks