Hello,
I need to say that I experience the same behavior as described by Bruno. When I deploy an installer containing VISA runtime on my development machine, Labview considers it to be the source of the VISA runtime when it builds an installer. Thus when I try to build an installer including the VISA runtime, it stops the build process and ask me to locate the source of the missing installer and shows me the name of the software installer believed to be the source. Unfortunately, it doesn't say at that moment that VISA is the missing installer, I had to find it by myself by adding and removing the additionnal installers from the build setup until I identified the problematic item.
I contacted NI about this issue and the havent come up with a working solution. They suggested to "Force reinstall Labview" which was unsuccessfull. Although it replaces all the files, it doesn't seem to do anything in the registry. The way I fixed it was by: 1- uninstall the problematic software, 2- manually delete all the registry keys refering to this software installer. (about 30) I did not take the time to identify the specific registry key that caused the problem.
I don't believe that repairing Labview files will do anything as the software installer doesn't modify any of these. Although I don't know exactly what lies under the Labview hood when it builds an installer, I believe it looks in the registry for the latest VISA runtime installer source. If it happends to come from a software installer, it will look for this installer. If it finds it, there is no problem, but if it doesn't it will ask you to locate the installer and if you don't have it anymore, it stops the build process.
If the installer is zipped and included in a self-extractor for easier deployement, it will unzip in a temp directory, install, and delete the installer files. It then becomes impossible for Labview to find these files. I have experienced this behavior with installers built on my own machine: I install it on my machine and it automatically becomes the VISA runtime installer source. Since then, I don't install Labview based installers on my development machine to avoid this problem.
