I have a internal library named A.dll build by VS2019, and I write a VS2019 application to test NIVISA's API and functionality A.dll.
The testing code is pretty simple, psudo code is like:
- Dynamic load visa64.dll
- GetProcAddress of viOpenDefaultRM/viOpen/viClose
- Call viOpenDefaultRM
- Call viOpen
- Call viClose
The flow run well in my environment, but once I load A.dll into project, I got viopen failed, the viopen error is like
Status code: 0xBFFF0011
Status name: VI_ERROR_RSRC_NFOUND
Insufficient location information or the device or resource is not present in the system.
It seems once I load A.dll into program's memory space. It would result in nivisa library's funciton call failed.
And the problem is the the viopen failed issue only happened after NI-VISA 17.5 version, it run pretty well before NI-VISA 17.0 version
Since it looks like an environment issue, I check the dependency walker and try some experiments on my environment and see it it could fix this issue.
Its even weird that once I copy the C:\Windows\System32\msvcp140d.dll and re-name it as msvcp140.dll and put it under the execution folder.
The problem solved under debug library of msvcp140.dll.
Can anyone expalins the difference between NI-VISA 17.0 and NI-VISA 17.5??
Also why I could only run with debug version of msvcp140.dll, is that any conflict in between NI-VISA 17.5 and Visual C++ runtime library (msvcp140.dll) ?
