In LabVIEW 8.6 and earlier, I am able to dynamically load VIs from disk files. There are some standard library VIs that would not load if they were called in the VI I was dynamically loading. To overcome this, all I had to do was call the library VIs somewhere in the compiled code, typically in a case structure that would not execute.
In LabVIEW 2012 & 2013, this method will not work. The only way I can dynamically load a VI is if I put the VI in the always include section of the build and load it from the .exe file. The problem with this is that if I make any changes in the dynamically loaded VI, I have to recompile the main application.
I remote support many test stands. On those with the older versions of LabVIEW, I can make a change in one of the dynamically loaded VIs and drop it on the test stand in the background while it is running. On the next test the change is automatically picked up when the VI is dynamically loaded again. With the new version of LabVIEW, I have to interrupt production, stop the machine, recompile and then restart the machine.
Below is sample code and an error I get in 2013 for VIs that will not load even though I have these in the .exe file. Anyone know a way around this?
