LabVIEW
LabView not working with NKT Laser
Hi hmyat,
hmyat@ucdavis.edu wrote:
LabVIEW Professional Development System Version 2022 Q3 (64-bit) 22.3f0We have attempted to fix this issue by downloading the newest SDK package and establishing a direct path to the .dll file both (x64) and (x86).
Is the DLL provided for 32bit or 64bit applications?
When the DLL is only available for 32bit applications then your LabVIEW-64bit cannot use it…
Btw. how do you "establish a direct path to the DLL file"?
hmyat@ucdavis.edu wrote:
The DLL is provided for 64bit applications.
For a direct path to DLL file, we currently have all the DLL files inside the folder: Program Files (x86)\National Instruments\LabVIEW 2020\instr.lib\NKTP_API\Private
That's most likely the problem. If your DLL depends on other DLLs that it needs Windows to load to work you can't put those DLLs wherever you like. The DLL referenced in the Call Library Node can have a path and LabVIEW knows to request from Windows to load a DLL from that specific part. But dependencies inside the DLL are only referenced by DLL name and then the standard Windows search rules for DLLs apply. The directory from the requesting DLL is very purposely NOT part of those search locations. If Microsoft could change history, they would reduce the search locations even more nowadays. It's a security nightmare to search all over the place for possible dependencies as it makes code injection almost trivial. If Windows can't find a dependency it aborts the whole load process and simply reports to the application that it couldn't load the DLL. No further details about why the load failed are available. LabVIEW did try in the past to detect more details by for instance checking if the file at the desired location really existed and if it looked like a DLL, to give a more differentiated return about if the loading failed because of dependencies or of a missing DLL itself, but that not only proofed difficult to make foolproof but also provides not a lot of useful information to the average LabVIEW user.
.Net assemblies are by default only searched in exactly two locations, the calling processes home directory and the Global Assembly Cache exactly for that reason. Trying to convince .Net to add other locations to the search path is an exercise in itself and requires quite a bit of effort once the process has been started with an Application Context.
.png){kind=link}
.png){kind=link}
