02-11-2026 03:35 AM
I am struggling building an application, this process has always been about trial and error for me. The code has vis that use an xml dll and ni845x.dll.
If I build without including the dlls in the support directory the .exe can’t run those vis due to missing dlls. So, I set the applicable project virtual folders to ‘Always Included’, destination to the support directory.
After app build, the xml functions now work but 845x functions still don’t due to missing dll. When I go to the support folder the ni845x.dll has not been included.
If I put any other file in a virtual folder and ‘Always Include’, it seems to be added to the support folder ok, apart from this one ni845x.dll file. I have checked and none of the dll calls have explicitly defined paths. I am running LabVIEW Pro Dev 2024 Q1 (32-bit).
So firstly, am I doing something fundamentally wrong? and secondly any ideas why this one dll can’t be included in support?
Only thing slightly out of the ordinary is that ni845x.llb (vi library using ni845x.dll) is installed in C:\Program Files\NI\LVAddons\... rather than under …LabVIEW 2024\..., and as above I am using the 32-bit LabVIEW version, i.e. base path C:Program Files (x86)\...
Solved! Go to Solution.
02-11-2026 08:32 AM
Ok so found the issue and it is 101 operator error.
Don't know if this will be of any use to anyone in the future but there are some dlls that can be included and some that cant because they have to be installed separately.
What I was trying to achieve was to build the Application, then run the .exe on a machine (with just LV runtime installed).
Then create the Installer based on the Application and test the full install process on the same machine.
However, the 845x.dll can only be installed as part of NI-845x Runtime install (as below). This can be done separately or as part of the Application Installer creation/install process (as below). Obvious when I thought about it for a bit.