07-05-2016 07:44 AM
So ive been reading the "not a tame lion" blog and I kind of liked his launcer based application. Where you have a central launcher to start a bunch of processes all in seperate VIs. This made sense for an application that needed two halves to do a network communication. Everything could be contained in the same executable and I would just change the config file to load the appropriate side.
This works great in development but when I build an executable and installer the folder structure isnt maintained so even though my paths are all referenced from the application directory where did the other part of the path to each VI go?
I just checked my build and ive included all the VIs to be launched in the always included box.
Thanks guys
Solved! Go to Solution.
07-05-2016 08:18 AM
I figured it out. when building the installer and selecting the source files you can click on the c drive drop down and see all the supporting files there.