LabVIEW
Labview runtime 2015 not showing in control panel
Do you have NI Max (Measurement & Automation Explorer) installed. It should have been installed if you installed NI DAQmx or other NI Data Acquisition software. If so run it and look under "Software" to see if it sees the LVRT. Also, sometimes the LabVIEW Runtime Engine shows up under the control panel "Programs and Features" outside of the National Instruments section, on its own.
That is what he is showing on his attached jpg image, his issue is that LVRT 2015 isn't showing up in the National Instruments section. I have recently seen where it does show up in the general list under the Programs and Features, rather than with all of the other NI installed programs.
bhavinsave - is your primary issue that something requiring LVRT 2015 isn't working?
Not to be funny, but does this dll work on any other machine? I ask because I spent much of last week trying to get a program to run on a "target machine", thinking there was an issue with my program, found that I had incorrect versions of other NI software installed, but the reverse can be true too. What is wrapper for the dll? Can you give more information on your use case? Do you have NI MAX installed? Can you see LVRT 2015 in MAX? Did you look in Control Panel: Programs and ... outside of the National Instruments section, in the main list? Is the "dll" compatible with the LVRT version you are trying to use? I also helped an associate with a problem they were having where they had built their exe with a different version of LabVIEW (in their case 2017 64bit, trying to run it with LVRT 2017 32bit).
Does your dll call any DAQmx or other "features" in LabVIEW? I'm pretty sure that 2015 sp1 should work backwards compatible with 2015. Can you make a simple vi, say a loop with a stop button, and build it into an exe, on you dev machine, then try it on the target? I don't build dll's in LabVIEW, so there is thin spot in my knowledge/experience.
Not comfortable with LabVIEW not showing up anywhere in Control Panel though. Not sure how your dll gets "associated" as a LabVIEW "program". What is the wrapper for the dll? How is it used?
I will be leaving shortly, will try to check back later this evening, there are others around the world that will be stopping in on the forums, it is morning in Asia as the sun sets here in the eastern US.
Do you have any error checking out of your dll, and is it passed out of the wrapper code? With the simple exe working it sounds like you have LVRT working, but that doesn't mean that needed resources are available for the dll. I my, somewhat different, case, not having the correct version of DAQmx meant a lot of missing DAQ sub-vi's, but this was indicated by a broken "Main" vi, which then listed what it was missing. If you have error handling in the dll and bring it out to the wrapper program, possibly handling that will tell us more. Do you know how the dll handles a bad path to the input file? Does it report that?
