09-01-2020 03:24 PM
When I built my application and put it on another computer, I get a 'Find the .NET Assembly Named "ULx_LV.dll" window, showing the file requested right there in the data folder.
Since it is in the correct folder, why can't LabVIEW find it?
I have built the application on Win 7 and trying to run in on Win 10.
I have looked the problem up, and found three solutions:
1. Make sure it is included in the build - it is.
2. Use a relative path to call the DLL - build a relative path in LabVIEW and this path will be valid in the deployed machine - I tried to move the file in project explorer, but can't because it's greyed out.
3. Make sure the DDL is not included in your user.lib library. In project explorer, the file is listed in the vi.lib folder under dependancies. - is this okay?
Please help.
09-01-2020 03:29 PM
Maybe you have to "always include" the dll?
09-01-2020 05:05 PM
You need to install ULx for LabVIEW on the other machine.
You might be able to get away with copying the DLL from the LabVIEW directory on your build computer into your source folder and including it in the build, but I'm not sure if that will install everything you need.
09-02-2020 07:21 AM
The file actually exists on in the directory that labview opens and requests I find, as shown below:
09-02-2020 09:07 AM
DLL's can be quirky. I suspect that LabVIEW is finding the dll, but then the dll is looking for other files.... I don't know. Either way, mccdaq says you need to install instacal and include some other files in the build.