This topic describes the structure of the LabVIEW file system and the suggested locations for saving files.
This section describes the structure of the LabVIEW file system on Windows, Mac OS, and Linux. LabVIEW installs driver software for GPIB, DAQ, VISA, IVI, Motion Control, and IMAQ hardware depending on platform availability.
The LabVIEW directory contains the following groupings after you complete the installation.
LabVIEW installs the vi.lib and the resource directories for LabVIEW system purposes only. Do not save your files in these directories.
You can save your files in the following directories:
![]() |
Note Save subVIs in the user.lib directory only if they are usable, without modification, across projects. Paths to VIs in user.lib are relative to the labview directory. Paths to subVIs you save elsewhere are relative to the parent VI. Therefore, copying a VI from user.lib to modify it for a special case does not change the path to its subVIs located in user.lib. |
If you want to copy a VI and its subVIs to another directory or computer, do not save the VIs in user.lib because when you run the top-level VI from the new location LabVIEW references the original subVIs in user.lib.
You also can create a directory anywhere on your hard drive to store LabVIEW files that you create.
When you open a VI you place in the labview\help, labview\project, and labview\wizard directories from the Help, Tools, or File menu, LabVIEW opens the VI in a private application instance (NI.LV.Dialog).
You also can use the Default:Application property to return the default application reference programmatically. Use the Application property to open the target application instance programmatically.