Necessary Files for Running Executable Programs

For your executable to run successfully on a target computer, all files the executable requires must be accessible. Your final installer must contain all of the following files to install your LabWindows/CVI executable program on a target machine.

• Executable—File that contains a precompiled, prelinked version of your LabWindows/CVI project and any instrument driver program files that you link to your project. The executable also contains the application title and icon resource to register to the operating system. The executable has an associated icon you can double-click to start the application. When the executable starts, it loads the runtime.
  
  

  (Linux) The executable returns the value that main returned or the value you passed to exit.

• Runtime—Runtime that contains all the built-in LabWindows/CVI libraries. The runtime consists of multiple files, including various DLLs and other support files.
• Hardware Drivers—Device drivers such as NI-DAQ and NI-VISA. You must install the hardware drivers if your project includes them.
• Hardware Configurations—If your project uses MAX-based DAQmx tasks, you must include them. These tasks are loaded using DAQmxLoadTask. In the Edit Installer dialog box Advanced tab, enable the Import Measurement & Automation Explorer configuration file option and select a hardware configuration file.
• DataSocket Server and Utilities—Server and its associated utilities that are required if your program uses the functions in the LabWindows/CVI DataSocket Library. Enable the DataSocket option in the Edit Installer dialog box Drivers & Components tab to include this installation in an installer.
• .uir files—The user interface resource files that your application program uses. Use LoadPanel, LoadPanelEx, and LoadMenuBar to load these files. You do not need to include .uir files if you have enabled the Embed project .UIRs option in the Target Settings dialog box.
• Image files—The graphical image files that you programmatically load and display on your user interface.
• State files—The user interface panel state files that you save using SavePanelState and load using RecallPanelState.
• DLL files—The Windows Dynamic Link Library files that your application program uses.
• Other files—Files your executable opens using open, fopen, OpenFile, and so on.
• ActiveX components—Any external ActiveX components that you use need to be included.
• ActiveX container—In the Edit Installer dialog box Drivers & Components tab, enable the Install ActiveX Container Support option if you use ActiveX controls in your .uir files.