Requires: Application Builder or Professional Development System
You can convert a LabVIEW project into a distributable application for use on other computers and from other programming languages. Complete the steps in this document to create any of the following types of distributable applications:
Note If your application contains VIs with separate compiled code, you can configure settings for those VIs on the Source Files Settings page of the Properties dialog box for your application. |
Note�If your application uses the 8.x file layout, you may need to use a different relative path on the destination computer from the relative path in the development environment. |
Note If you save a custom run-time menu for a front panel control as a separate run-time menu file, or .rtm file, and want to include this control in an application build, you must add the .rtm file to the Always Included listbox on Source Files page of the Properties dialog box for your application. |
Note If you want to include any type of application within an installer, make sure to specify that all the files in the application are relative to the primary destination of the application. Otherwise, when you include the build output of the application within an installer, the installer will reorganize the original file organization of the application by moving all files that are not relative into the primary destination. You can specify the primary destination for any type of application on the Destination page of the Properties dialog box for the application. |
If a VI loads other VIs dynamically using the VI Server or calls a dynamically loaded VI through a Call By Reference or Start Asynchronous Call node, you must add those VIs to the Always Included listbox on the Source Files page of the Properties dialog box for your application.
Right-click the build specification name for the application you want to build, and select Build from the shortcut menu. You also can build an application programmatically using the Build VI or the ExecuteBuildSpec command line operation.
Tip��You can preview your application to ensure that it appears correctly. From the Preview page of the Properties dialog box for your application, click the Generate Preview button to review the generated files for your application. |
Action | Benefit | ||
---|---|---|---|
To verify that the built application performs correctly, enable debugging by placing a checkmark in the Enable Debugging checkbox on the Advanced page of the Properties dialog box for your application. You also can connect to a built application by selecting Operate»Debug Application or Shared Library. | When you test a built application, you ensure that behavior did not change between the development environment and the distribution environment. | ||
After you test your application, disable debugging for your VIs. | Disabling debugging for VIs can reduce file size and increase run-time performance. | ||
Create an About dialog box for a stand-alone application. | Most professional applications include an About dialog box that provides general information about the application, such as version, copyright, and support information. | ||
If your end user has spoken language requirements that differ from the language of the original application, adjust the default language settings for the application on the Run-Time Languages page of the Properties dialog box for your application. | When you distribute an application, dialog boxes and menus adopt the spoken language of the operating system on which the application runs, but the text and controls you implement remain in the language of the operating system on which you originally built the application.
By default, stand-alone application and shared library build specifications provide support for Chinese (Simplified), English, French, German, Japanese, and Korean. | ||
If your application uses the same VI Server port as another application, create a custom configuration file. | If you try to run an application that requires the VI Server at the same time as the conflicting application, the VI Server does not run, and LabVIEW does not provide a warning. | ||
Distribute a custom configuration file along with your built application. | If you need to ensure that the application always runs under certain LabVIEW environment settings, you can preserve and redistribute those settings by distributing a custom configuration file, or preference file, with your application. |