This content is not available in your preferred language.

The content is shown in another available language. Your browser may include features that can help translate the text.

Using a Custom .ini File for a LabVIEW Executable

Updated Feb 13, 2026

Reported In

Software

  • LabVIEW Application Builder Module
  • LabVIEW Base
  • LabVIEW Full
  • LabVIEW Professional

Issue Details

  • Is it possible to deploy a user-defined .ini file with a LabVIEW executable?
  • I have a LabVIEW VI that I have built into an application. I would like to replace the default <Executable Name>.ini file with a custom .ini file. How can I do this?

Solution

You can use Application Builder to replace the default application .ini file with a custom .ini file. You must first ensure that:

  1. The custom .ini file already exists on disk.
  2. The custom .ini file is included in the LabVIEW project, as shown below.
    • To add a file to a LabVIEW project, right-click My Computer and select Add >> File... Then browse to the location of your file on disk.

 

You must include an .ini file that already in the LabVIEW project in order to add it to the Build Specifications.




Once the custom .ini file is included in the project, follow the steps below to deploy this file with the executable:
 

  1. Right-click on your executable Build Specification and select Properties.
  2. In the properties window, select the Advanced category.
  3. In the configuration file in project section:
3.1. For LabVIEW 2010 and later: Check Use Custom Configuration file            
3.2 Prior to LabVIEW 2010: Uncheck the box next to Use the default LabVIEW Configuration file (LabVIEW.ini)


4. In the Select Project File dialog, either select the custom .𝚒𝚗𝚒 file if it is in your project or click Add... to browse for it.
5. If you are using Configuration File I/O VIs from the palette below:

Ensure that all of your configuration file accesses within your application point to the new location which is at the same level as the executable, as shown below:
 
6. Rebuild the application.
7. Note: The name of the .ini file generated from the build will match the name of the executable. It may be necessary to rename the file to match the name of the .𝚒𝚗𝚒 file referenced by your LabVIEW code in the 𝙾𝚙𝚎𝚗 𝙲𝚘𝚗𝚏𝚒𝚐 𝙳𝚊𝚝𝚊.𝚟𝚒 as shown above. After renaming the .𝚒𝚗𝚒 file generated, the final result should look like this: 

Additional Information

On the deployed machine, the custom .𝚒𝚗𝚒 file and the executable must be located at the same level in the directory structure because this is the default location where LabVIEW searches for the .𝚒𝚗𝚒. If LabVIEW cannot find it in this location it will auto-generate a new .𝚒𝚗𝚒 file and your environmental settings will be lost.