Deploying dependency VIs in a static location

[NandaNIProfile]

Hi,

I am looking for a way to link the dependency VIs of the Exe in a static location, so that even if I move the Exe to some other location, I don't need to move the dependency VIs. Exe would just need to access the dependency VIs from the static location.

Assume my application has a vi "Main.vi", which am going to build in to an Exe. Main.vi calls two other sub VIs "1.vi" and "2.vi". While building an Exe "main.exe" in "C:\builds" folder, I have added a new destination in "C:\" and all the sub VIs are build to the "C:\". Not if I copy the "Main.exe" to some other location of different folder hierarchy, it doesn't loads the sub vis. 

The reason being for this post is in future I may modify my sub vis and don't want to rebuild my exe. Is there a way to achieve this? Should sub VIs used in the Exe be always in the relative location?

Regards

[aeastet]

You could move them to the C:\Program Files\National Instruments\LabVIEW 2011\user.lib. If you do this they will even show up on your palette for use later. This is what I do for all of my reuseable code. I also use a software managment tool for backups to prevent losing a file.

[NandaNIProfile]

Tim,

Thanks for your reply. Moving those sub vis to the user lib works fine when we are dealing with soure code. When we build EXE, these vis in the user lib would either build inside the exe or can be moved to another destination say a data folder. The link between Exe and these sub vis are now on  relative path. Meaning if i move the exe to some other location, exe would not work. I wanted to make this link to a static path, say "C:\Sub vis" or "user lib" folder.

Regards.