06-10-2010 03:45 AM
Solved! Go to Solution.
06-10-2010 04:52 AM
The problem seems to be that the LAS SDK .net assembly is not GAC registered. Therefore a copy will be generated in your build folder.
1) If the LAS SDK .net assembly is strong name key signed you can register it yourself using the gacutil cmd from the MS SDK.
2) If it's not signed try to disassemble it with ildasm and re-assemble and sign it with ilasm
Hope it helps
06-10-2010 01:54 PM
It's being placed into the Data folder because it shows up in the list of dependencies, and the data folder has a default target of being in the location where the application is created. The reason why it doesn't work in the app is that there is a dependency. One or more other .NET private assemblies from the folder where the one you're using is are required.
The .NET Runtime (CLR) is what is responsible for finding .NET assemblies, so LabVIEW doesn't have anything to do with finding other assemblies. In this respect, .NET has specific rules it follows on locating assemblies.
The simplest solution to your problem is to include all the .NET assemblies from that folder into your project. That way they can get copied into the data folder when you build the project.
08-20-2012 08:59 AM
I'm having the same problem.
Unfortunatly when I include the entire folder (containing all the DLL and system files I need) it doesn't work.
Is there a simple way to reference a .dll file from the computer instead of having it in the data folder? I installed a driver that comes with a .dll and it would be easier to have my application reference the location where that .dll resides. It's working on my development computer but now on my deployment computer.