How to get hold of all vi's that have been used in an application?

[Rodnebb]

I've now made a program, it's about to be shipped to the customer and all's finished and well.

Now all I have to do is to archive the sourcecode for future reference.

I am however worried that I won't get hold of all the relevant vi's that I've used. Some have come from NI's examples while others from the OpenG package etc. These vi's then use other sub vi's, and are located in the NI directory structure (under Program Files).

Is there an automated way of collecting all subcode and putting it in one folder, so that I can be sure I will always have it?

Thx

[craigc]

Hi,

Dont Quote me on this but have you looked under the "save as" options.  There is one there that states "Duplicate hierachy to new locationfolder".  Mayby this could be used to archive your source code.  I have not used this and it does not copy vi's from the vi.lib  I will need to do this in the future so am keen to know if there is another method also.

Craig.

[Jim_Kring]

---

@Rodnebb wrote:

I've now made a program, it's about to be shipped to the customer and all's finished and well.

Now all I have to do is to archive the sourcecode for future reference.

I am however worried that I won't get hold of all the relevant vi's that I've used. Some have come from NI's examples while others from the OpenG package etc. These vi's then use other sub vi's, and are located in the NI directory structure (under Program Files).

Is there an automated way of collecting all subcode and putting it in one folder, so that I can be sure I will always have it?

Thx

---

Hi,

VI Package Manager 1.1 Professional solves the problem for the OpenG packages and other libraries installed using VIPM (VI Package Manager).  VIPM can scan your project and identify which OpenG packages your project is using and save the packages into a VIPC (VI Package Configuration) file, which you can save in your project folder.  When you are ready to start working on your project again, you can apply your VIPC file to have VIPM install all the required packages.

I have written a blog post, here, about the new configuration management capabilities in VIPM 1.1 Professional.  I hope this helps.

Thanks,

-Jim Kring

[Rodnebb]

To partially answer my own question:

If you select "File/Save as... / Duplicate Hierarchy in new location" then it is possible to the current vi plus all referenced vi's saved to a new folder.

Only problem seems that the lvproj file doesn't come along, so this one must be copied along or created anew (?).