LabVIEW 2018 Help
View Product Info
DOWNLOAD (Windows Only)
Requires: Application Builder or Professional System
Use this page of the Application Properties dialog box to configure advanced settings for a stand-alone application.
This page may include the following components:
- Enable debugging—Enables debugging for the application, shared library, .NET interop assembly, or Web service.
|Note Disabling this checkbox does not ensure full optimization.|
- Wait for debugger on launch—Sets the application, shared library, or .NET interop assembly to load but not run until the user enables it to run through the LabVIEW debugging controls. Place a checkmark in the Enable debugging checkbox to enable this option.
- Use fast file format—Saves the stand-alone applications (EXE) or shared libraries (DLL) in a format that loads faster. To use the fast file format, ensure that the Enable debugging checkbox on the Advanced page does not contain a checkmark.
The fast file format does not support applications that contain 3D graphs. When you enable the fast file format, LabVIEW does not use the Application Builder object cache. Therefore, stand-alone applications and shared libraries may take longer to build.
- Copy error code files—Adds copies of XML-based LabVIEW error code text files from the project\errors and user.lib\errors directories to the run-time engine.
|Note You must manually create an errors folder in the labview\user.lib directory to organize your error code files.|
- Use custom aliases file—Copies the project aliases file with the application, shared library, or .NET interop assembly. If you place a checkmark in the checkbox, the Select Project File dialog box appears and you can select an aliases file in the project.
- Aliases file in project—Specifies the aliases file to use with the application, shared library, or .NET interop assembly if you select Use custom aliases file.
- Browse Project—Displays the Select Project File dialog box, which you can use to select an aliases file.
- Use custom configuration file—Associates the LabVIEW configuration file with the application. If you place a checkmark in the checkbox, the Select Project File dialog box appears and you can select a configuration file in the project.
If you do not place a checkmark in this checkbox, you can change the default settings for the build using the VI Server page of the My Computer Properties dialog box or (Windows Embedded Standard) Target Properties dialog box and using the Visible VIs and Browser Access lists on the Web Server page of the Options dialog box.
- Configuration file in project—Specifies the configuration file to use with the application if you enable Use custom configuration file.
- Browse Project—Displays the Select Project File dialog box, which you can use to select a .ini file in the project.
- Pass all command line arguments to application—Passes all arguments as user-defined arguments to the application when you launch it from the command line. Only the arguments after two hyphens (--) in the command line pass to the application as user-defined arguments, unless you place a checkmark in the checkbox. Use the Application:Command Line Arguments property to read the user-defined command-line arguments passed when the application launches.
- Enable ActiveX server—(Windows) Enables the ActiveX server so the application can respond to requests from ActiveX clients. The functionality of the ActiveX server in the application is a subset of the LabVIEW ActiveX server. When you build an application myapp.exe, Application Builder also creates an ActiveX type library myapp.tlb. The type library defines an application class and a virtual instrument class and exports both Application properties and methods and VI properties and methods. When you distribute the application, include the type library with the executable file.
The name of the application that you enter in the ActiveX server name text box uniquely identifies the application in the system registry. After you build the application, run it at least once to enable registry with the system. After the application is registered, ActiveX clients access the server objects using progIDs. For example, if the ActiveX server name is myapp, clients instantiate an application object using the progID myapp.application.
If you are packaging the application into an installer build specification, place a checkmark in the Register COM checkbox for the application file on the Source File Settings page of the Installer Properties dialog box so the installer registers the ActiveX server.
|Note If you enable the ActiveX server, you must save the application build specification after you build the application for the first time.|
- ActiveX server name—(Windows) Specifies the prefix of the progID for the application. This text box is enabled when you place a checkmark in the Enable ActiveX server checkbox.
- Include target hardware configuration—Specifies to include the configuration settings for the target to which you deploy this application. If you place a checkmark in this checkbox, LabVIEW queries the project to retrieve the configuration settings for the target and includes the configuration settings with the application.
- Enable Enhanced DSC Run-Time support—This option only appears if you have the LabVIEW Datalogging and Supervisory Control (DSC) Module installed. Builds the application with the enhanced DSC Module Run-Time Engine. The DSC Module Run-Time Engine adds additional support for programmatic project library and shared variable management in applications that you build with the DSC Module. You must place a checkmark in this checkbox in the following situations:
- The application you want to build uses VI Server references to modify a library file programmatically.
- The application you want to build uses the Save to Library VI.
If you do not enable the enhanced DSC Module Run-Time Engine in these two situations, LabVIEW returns error code 1055 when you run the built application, shared library, or .NET interop assembly.
|Note Enabling this option increases the file size and reduces the start-up performance of the built application, shared library, or .NET interop assembly.|
- Generate build log file—Specifies whether to create a log file for the build. The build log file lists all files contained in the build, including subVIs you do not specify as Startup VIs or Always Included. The log file also contains general build information such as build start and end time, the build specification and project name, and any errors that occurred during the build.
- Log file path—Specifies the path to save the build log file.
- Use LabVIEW 8.x file layout—Specifies to use a flat file layout to store source files inside a stand-alone application, shared library, or Web service. LabVIEW enables this option by default for build specifications you load from LabVIEW 8.6 or earlier. National Instruments recommends you disable this option for applications you develop in LabVIEW 2009 or later.
- Allow future versions of the LabVIEW Runtime to run this application—Enables this application to run with future versions of the LabVIEW Run-Time Engine. You can disable this option to bind a build specification to a specific version of LabVIEW. Disabling this option prevents any changes to the performance profiles and helps you avoid unexpected problems resulting from compiler upgrades.
Building and Distributing Applications Home