LabVIEW Wiki - User contributions [en]

Application Builder

2019-07-13T00:13:32Z

Greggers89:

{{TOCnestright}}

= Introduction =
The application builder (AB) is a part of the LabVIEW Project environment, it has the possibilities to distribute your code in various ways: 

*Executables 
*DLLs 
*Source distributions 
*Web services 
*Installers 
*Packages 

Depending on the LabVIEW version you have one or more of the above options might be missing.

= Manual =
{{Stub}}
= Advanced =

The application builder has several interesting advanced uses 

== Automatic building ==
You can use a VI inside vi.lib that can build without user interaction. The VI is located in <''vi.lib>\AppBuilder\BuildTargetBuildSpecification.vi''. This VI takes a project path and optionally a build and target name as parameters. 

== Symbolic paths ==

Inside the application builder LabVIEW uses several symbolic paths to have envorinment dependent variables.

{| cellspacing="1" cellpadding="1" border="1" style="width: 708px; height: 104px;"
|-
! scope="col" | Symbolic path 
! scope="col" | Contents 
! scope="col" | Usage 
|-
| NI_AB_PROJECTNAME 
| Name of the project 
| Automatically place the build in a folder that is named after the project
|-
| NI_AB_TARGETNAME 
| Name of the (Real-Time) target 
| 
|}

[[Category:Building executables]]

LVPROJ File Extension

2019-07-13T00:12:24Z

Greggers89:

The '''LVPROJ File Extension''' (''*.lvproj''), or LabVIEW Project, consists of a description of [[VI|VIs]], files necessary for those VIs to run properly, and supplemental files such as documentation or related links. [[LabVIEW Project|LabVIEW Projects]] also define build and distribution parameters. Use the [[Project Explorer]] window to manage projects in LabVIEW.

See [[LabVIEW Project]]

==See Also==
*[[Project Explorer]]

[[Category:LabVIEW file extensions]]

Call By Reference

2019-07-13T00:08:37Z

Greggers89:

The '''Call By Reference''' Node is used to call VIs with a specified connector pane, but without exactly specifying the VI ''at edit time''. It can be used to provide a plug-in architecture within an application, where the actual plug-in can be choosen ''at runtime''. The number of and the specific plug-ins can be changed at any time after the calling application has been finished. 
The [[VI Reference]] used with Call By Reference must be a strictly typed reference, which can be obtained using the Open VI Reference Node. 
Aside of the [[VI Reference]] and the [[Error Cluster]] flow-through connectors, there is a specific connector pane that relates to the strictly typed VI Reference, both with the connector pane and with their data types. You can wire to these terminals just as you would to a normal subVI. 
Be aware that calling a VI with the '''Call By Reference''' Node involves a small overhead compared with a normal SubVI call, due to validating the [[VI reference]] and some other bookkeeping. This is, however, insignificant with all but very small VIs when used on local machines. It can become a problem with frequent calls to remote machines.

[[Category:Application control]]
[[Category:Calling a VI]]