Hello all you helpful forum-goers!
I have created an installer for my LabVIEW software, and used the "Run executable at end of installation" feature to run a batch file to copy some files into the installation directory afterwards. This setup allows me to change the files that are copied afterwards without having to rebuild the installer, which means I don't have to reconfigure it with CM or rerun the installer-specific tests.
However, doing it this way means that the installer version has not changed, and if I give someone the same installer with different files to copy over, the installer appears to exit without running the post-install batch file.
I understand that a relatively simple work-around would be to give the customer the new files separately without involving the LabVIEW installer, and instruct them to place the new files in the correct Program Files subdirectory, but for the purpose of consistency in how we deliver to our customers, is there any way to get the installer to run the post-install batch file regardless? Or is there anything else about the situation I'm misunderstanding?
Thank you for your time and assistance!
-Joe
P.S. It also occurred to me that I could set up a batch file to copy the files and then run the LabVIEW installer, but that involves changing other parts of our standard setup (i.e. changing the autorun.inf file to call the batch file instead of setup.exe and other changes like that, so I'd like to see if there is an easier solution first.
