LabVIEW Project

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 Project Explorer

Contents

The contents of a project is seperated 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:

1. Code
2. Dependencies
3. Build specifications

Code

Items under a target represent links to actual files, these files can be rearranged inside the LabVIEW project to have a better seperation like VIs, controls or libraries. Moving things around inside the LabVIEW project will not alter the files or there location except when the files are added or removed from a library-file.

Dependencies

Dependencies are files used by files inside the code section and not explicitly added to the project. LabVIEW 8.5 and up have seperate categories for vi.lib, user.lib and instr.lib.

Build specifications

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.

Project Item

Folders

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.

GUID Index

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.

Item type	Type String	GUID String
Virtual Folder	Folder	{D60740D6-F254-4BBC-5675-8858F35B820E}
Auto Populating Folder	Folder	{D60740D6-F254-4BBC-5675-8858F35B820E}
VI	VI	{D60740D6-F254-4BBC-5675-8858F35B810E}
Control	VI	{D60740D6-F254-4BBC-5675-8858F35B810E}
(Non-LabVIEW) file	Document	{D60740D6-F255-4BBC-5675-8858F35B820E}
LLB-file	Folder	{D60740D6-F254-4BBC-5675-8858F35B820E}
Lvlib file	Library	{ABC740D6-F254-4BBC-5675-8858F35B820E}
LabVIEW class	LVClass	{EFD740D6-F254-4BBC-5675-8858F35B820E}
Class datatype	Class Private Data	{64A9BF48-4C55-45DB-8F18-9C796DA0C113}
LabVIEW XControl	XControl	{2E4BD3AC-4E04-45C9-B6C5-AD138962C435}
XControl ability VI	Ability VI	{DAABD3DA-4F44-4C3D-8BA3-E5D035A4F27A}
DAQmx Task	NI-DAQmx Task	{0A806145-1BF3-3A50-0B5E-F969F56C8E2A}
DAQmx Virtual Channel	NI-DAQmx Channel	{B5F05770-7C71-3A03-C9FB-F73F35629FC1}
DAQmx Scale	NI-DAQmx Scale	{BC977C97-1833-3D51-4EF6-D82E6838A8F3}
Shared NetworkVariable	Variable	{9BA597C5-4996-4622-B9BB-444431834D0D}
Hyperlink	Hyperlink	{CC472C20-0441-48DC-AF25-3E82ECC9376F}

External Links

• Using LabVIEW Projects (NI LabVIEW 8.6 Help)
• Incompatibility of Auto-Populating folders and LabVIEW libraries