About LabVIEW Projects
A LabVIEW Project is a tool for organizing project files, NI hardware, configuration data, and build specifications. Project information is stored in an .lvproj file.
The "Project Explorer" window, shown below, is where you interact with LabVIEW projects:
The contents of a project is separated into Targets. Each target represent a platform on which the code will run, for instance Real Time modules.
Under each target three subdivisions are made:
- Build specifications
Items under a target represent links to actual files, these files can be rearranged inside the LabVIEW project to have a better separation like VIs, controls or libraries. Moving things around inside the LabVIEW project will not alter the files or their location except when the files are added or removed from a library-file.
The build specifications contains setting for distributing the code in several forms as a toolkit (source distribution), executable (exe), shared library (DLL) or web-app.
These builds can be included in an installer.
Elements in a project can be organized using folders. (The original LabVIEW project implementation (LabVIEW 8.0-8.2) only allowed so called Virtual folders where there was no connection between the project folder or a disk folder.) Upon user request LabVIEW 8.5 added support for Auto-Populating folders. These folders are a shortcut to a folder on a disk and will include all the files inside that folder (including sub-folders). Mixing Auto-Populating folders with LabVIEW library folders is not recommended and might cause cross-links.
For any Project Item a Type string and GUID string can be obtained using VI server. The following table lists the GUID for several Project Item types.
|Auto Populating Folder
||Class Private Data
|XControl ability VI
|DAQmx Virtual Channel
- Using LabVIEW Projects (NI LabVIEW 8.6 Help)
- Incompatibility of Auto-Populating folders and LabVIEW libraries