Follow the guidelines for distributing a build output that you create from a build specification with LabVIEW.

  1. Ensure that the computer on which you want to run the build output has access to a compatible version of the LabVIEW Runtime.
    Note The LabVIEW Runtime must be installed on any computer on which users run an application or shared library. You can distribute the LabVIEW Runtime with the application or shared library. On Windows, you can include the LabVIEW Runtime in an installer
  2. Distribute legal information for your end user.

    If you use installers to distribute your applications, enter information for a custom license agreement on the Dialog Information page of the Installer Properties dialog box. Review <National Instruments>\_Legal Information.txt for information about including legal information in installers built with NI products.

  3. Refer to Table 43. Guidelines for Distributing Build Outputs for tips to assist you with distributing build outputs that you create with LabVIEW.
    Table 43. Guidelines for Distributing Build Outputs
    Objective Action
    Determine that application behavior has not changed between the development environment and the distribution environment 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.
    Reduce file size and increase run-time performance After you test your build output, disable debugging for your VIs.
    Provide information about a stand-alone application 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.
    Support different user interface languages 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 build output, if present.

    When you distribute a build output, 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 created the build output.

    By default, stand-alone application and shared library build specifications provide support for Chinese (Simplified), English, French, German, Japanese, and Korean.
    Prevent VI Server port conflicts for stand-alone applications If your stand-alone application uses the same VI Server port as another stand-alone 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.
    Apply specific LabVIEW environment settings when distributing the application Distribute a custom configuration file, or preference file, along with your built application.