LabVIEW Project and saving only the relevant vis

Question

I have a large development folder (and sub-folders) that I have used as a repository for all of my development plus test pieces of code. There are about 800 vis in the folder, but if I save my main VI off to another folder using "Duplicate Hierarchy to new location" I end up with 150 or so relevant files.  Unfortunately I have not discovered an easy way of copying the project over to the new location.
What I'm looking for is the ability within the project file to go through all of the files that in the project, determine if they are used in the VI hierarchy, transfer those files to my new location along with the project files. And then also reference all files in the new location, not the old.  This way I could build a number of slightly different programs, but which uses the whole power of my development vis that I may have already.
Dan

Answer 1

Peter_B wrote:
Ben wrote:
I'd start by creating a source distribution in the project (use perserve hiearchy) based on the top level VI or if that is not enough create a Tree.........
A similar problem has stumped me for years and relates closely to the solution you pose Ben.
I am frustrated that LabVIEW doesn't allow me to include the lvproj file into the source distribution.  I used to be able to do it in LV2009 via a workaround (I'd put the lvproj file into a subdir of the highest commmon DIR where all the project files reside on disk), but now LV 2010 intentionally seeks out and excludes my lvproj wherever I try to hide it !!
This article from NI Source Distribution Does Not Include LabVIEW Project File tells me to use the zip file distribution method instead.  Well, that ain't a solution for me as zip file distributions don't have:
the 'Always Excluded' pane in the Source Files menu (there are project files that I don't need to distribute),
the 'Additional Exclusions' menu item as for some reason there are a heap of vi.lib files also included into this zip (which I don't want or need).  
Yes I still that was a bad idea by NI.
I did try to log a bug about that but was fed some line about including the .proj file was not part of thier use case so... I think their use case is flawed, still.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction