|
|
| Line 1: |
Line 1: |
| {{wikify}} {{update}} {{cleanup}} | | {{underconstruction}} |
| == About LabVIEW Projects ==
| |
|
| |
|
| {{TOCright}} | | {{TOCright}} |
|
| |
|
| A [[LabVIEW_Project|LabVIEW Project]] is a tool for organizing project files, NI hardware, configuration data, and build specifications. Project information is stored in an .lvproj file. | | A '''LabVIEW Project''' is a file with extension (''[[LVPROJ File Extension|*.lvproj]]''). It is an XML file that stores information about the files, targets, hardware configurations, and build specifications that makeup a project. The [[Project Explorer]] is used to view and edit these files. It is not recommended to edit the XML directly. |
| | |
| The "Project Explorer" window, shown below, is where you interact with LabVIEW projects:
| |
| | |
| [[Image:Project Explorer.png|frame|center|550px|The Project Explorer]] | |
| | |
| === Contents ===
| |
| | |
| The contents of a project <span style="font-style: italic;">is </span><span style="font-style: italic;">separated into </span>''Targets''. Each target represent a platform on which the code will run, for instance Real Time modules.<br>
| |
| | |
| Under each target three subdivisions are made:
| |
| | |
| #Code
| |
| #Dependencies
| |
| #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 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.
| |
| | |
| ==== Dependencies ====
| |
| | |
| Dependencies are files used by files inside the [[LabVIEW Project#Code|code]] section and not explicitly added to the project. LabVIEW 8.5 and up have separate categories for [[Vi.lib|vi.lib]], [[User.lib|user.lib]] and [[Instr.lib|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<br> ===
| |
| | |
| ==== Folders<br> ====
| |
| | |
| 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 link|cross-links]].'''<br>'''
| |
| | |
| <br>
| |
| | |
| ==== GUID Index<br> ====
| |
| | |
| 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.<br>
| |
| | |
| {| cellspacing="1" cellpadding="1" border="1" style="width: 551px; height: 103px;"
| |
| |-
| |
| ! scope="col" | Item type<br>
| |
| ! scope="col" | Type String<br>
| |
| ! scope="col" | GUID String<br>
| |
| |-
| |
| | Virtual Folder<br>
| |
| | Folder<br>
| |
| | {D60740D6-F254-4BBC-5675-8858F35B820E}<br>
| |
| |-
| |
| | Auto Populating Folder<br>
| |
| | Folder<br>
| |
| | {D60740D6-F254-4BBC-5675-8858F35B820E}<br>
| |
| |-
| |
| | VI<br>
| |
| | VI<br>
| |
| | {D60740D6-F254-4BBC-5675-8858F35B810E}<br>
| |
| |-
| |
| | Control<br>
| |
| | VI<br>
| |
| | {D60740D6-F254-4BBC-5675-8858F35B810E}<br>
| |
| |-
| |
| | (Non-LabVIEW) file<br>
| |
| | Document<br>
| |
| | {D60740D6-F255-4BBC-5675-8858F35B820E}<br>
| |
| |-
| |
| | LLB-file<br>
| |
| | Folder<br>
| |
| | {D60740D6-F254-4BBC-5675-8858F35B820E}<br>
| |
| |-
| |
| | Lvlib file<br>
| |
| | Library<br>
| |
| | {ABC740D6-F254-4BBC-5675-8858F35B820E}<br>
| |
| |-
| |
| | LabVIEW class<br>
| |
| | LVClass<br>
| |
| | {EFD740D6-F254-4BBC-5675-8858F35B820E}<br>
| |
| |-
| |
| | Class datatype<br>
| |
| | Class Private Data<br>
| |
| | {64A9BF48-4C55-45DB-8F18-9C796DA0C113}<br>
| |
| |-
| |
| | LabVIEW XControl<br>
| |
| | XControl<br>
| |
| | {2E4BD3AC-4E04-45C9-B6C5-AD138962C435}<br>
| |
| |-
| |
| | XControl ability VI<br>
| |
| | Ability VI<br>
| |
| | {DAABD3DA-4F44-4C3D-8BA3-E5D035A4F27A}<br>
| |
| |-
| |
| | DAQmx Task<br>
| |
| | NI-DAQmx Task<br>
| |
| | {0A806145-1BF3-3A50-0B5E-F969F56C8E2A}<br>
| |
| |-
| |
| | DAQmx Virtual Channel<br>
| |
| | NI-DAQmx Channel<br>
| |
| | {B5F05770-7C71-3A03-C9FB-F73F35629FC1}<br>
| |
| |-
| |
| | DAQmx Scale<br>
| |
| | NI-DAQmx Scale<br>
| |
| | {BC977C97-1833-3D51-4EF6-D82E6838A8F3}<br>
| |
| |-
| |
| | Shared NetworkVariable<br>
| |
| | Variable<br>
| |
| | {9BA597C5-4996-4622-B9BB-444431834D0D}<br>
| |
| |-
| |
| | Hyperlink<br>
| |
| | Hyperlink<br>
| |
| | {CC472C20-0441-48DC-AF25-3E82ECC9376F}<br>
| |
| |}
| |
| | |
| <br>
| |
| | |
| <br>
| |
| | |
| == Tips and tricks ==
| |
| * Select '''Arrange By''' from the right-click menu of a folder to choose between different sorting options.
| |
| * Drop any file into the '''Project Explorer''' to add it to the project. This also works for multiple files and folders.
| |
| | |
| == External Links ==
| |
| | |
| *[http://zone.ni.com/reference/en-XX/help/371361E-01/lvconcepts/using_labview_projects/ Using LabVIEW Projects] (NI LabVIEW 8.6 Help)
| |
| *[http://forums.lavag.org/False-linking-of-VIs-to-svn-folder-t12757.html# Incompatibility of Auto-Populating folders and LabVIEW libraries]<br>
| |
|
| |
|
| [[Category:Project]] | | [[Category:Project]] |
A LabVIEW Project is a file with extension (*.lvproj). It is an XML file that stores information about the files, targets, hardware configurations, and build specifications that makeup a project. The Project Explorer is used to view and edit these files. It is not recommended to edit the XML directly.
