Why License Folder Included With Executable Built Using LabVIEW Application Builder

Updated Sep 30, 2024

Reported In

Software

  • LabVIEW Application Builder Module

Issue Details

  • I built an installer for my empty LabVIEW project and found a license folder consisting of a variety of licenses. Why it is included and how to avoid it?
  • I have numerous LV projects, and when distributing them as an installer, some of them have a license folder with contents, and some of them do not have any contents. The license folder is located at ..\builds\Project Name\Installer Name\Volume\license . Is this a bug?

Solution

This is expected behaviour. In the installer's properties, there is an option for the developer to distribute the installer with or without the runtime engine needed to run the application. This option can be found by right-clicking the installer>>Properties>>Additional Installers, as illustrated below.
image.pngBy default, automatically select recommended installers option is selected. In this case, LabVIEW automatically selects recommended additional installers to distribute with an installer based on the build specifications on the Source Files page. Even if an empty VI is being distributed, a LabVIEW Runtime Engine will be included. When LabVIEW Runtime Engine is included, the end-user will find licenses in the license folder at ..\builds\Project Name\Installer Name\Volume\license. If the automatically select recommended installers option is not selected, and no additional installer is included, the license folder will be empty.

Related Links

Other Support Options

Ask the NI Community

Collaborate with other users in our discussion forums



Request Support from an Engineer

A valid service agreement or active software subscription may be required, and support options vary by country.