|LabWindows/CVI 2010 Help|
|LabWindows/CVI 2012 Help|
|LabWindows/CVI 2013 Help|
|LabWindows/CVI 2015 Help|
|LabWindows/CVI 2017 Help|
|LabWindows/CVI 2019 Help||LabWindows/CVI 2020 Help|
Use the Files tab of the Edit Installer dialog box to specify what files the installer application installs and where it installs these files. The Local Files & Directories browser displays the files and directories on the local machine. The Project Files item in the directory tree provides quick access to all the files associated with each project in the workspace. The Installation Files & Directories browser displays the files and directories to install, which are symbolic locations that resolve to the proper paths on the installation computer. Browse under the My Computer folder to access additional files. When you select a folder in one of the trees, LabWindows/CVI displays the contents of the selected folder in the files table.
LabWindows/CVI automatically adds the project output, project DLL dependencies, and any other project files (excluding .h, .c, .fp, and .lib files) to the Installation Files & Directories browser.
You can add files to the installer in the following ways:
|Note Do not install multiple .inf files in one directory. If you have multiple .inf files, create a separate directory for each .inf file. Do not explicitly install your file to the Windows .inf store; it will be implicitly registered and copied to the Windows .inf store during installation.|
|Note Do not install DLLs for NI components manually. Instead, use the Drivers & Components tab, which ensures that the installer you are creating supports upgrades and does not uninstall needed files.|
The Project Name Bitness Output items represent the release executable, DLL, or static library built by the default configurations of your project. The naming convention for output items built from custom configurations is Project Name Configuration Output. Output items dynamically update based on the current target type and settings of the project.
|Note In 32-bit installers, output items for 32-bit release configurations are displayed in the Local Files & Directories browser. In 64-bit installers, all release configuration output items are displayed.|
For a DLL project output group, you can toggle the inclusion of the import library by right-clicking the item and selecting Include/Exclude Import Library.
The DLL dependencies items list DLLs that the LabWindows/CVI linker detects are required for the project. These dependencies typically result when the project includes import libraries or instrument drivers that are associated with DLLs. If LabWindows/CVI does not detect any required DLLs, LabWindows/CVI does not list any DLLs and the size for these items is zero. You must build the project configuration for LabWindows/CVI to populate the corresponding dependencies items with files.
The Project Name Bitness Dependencies items represent the dependencies of the release executable, DLL, or static library built by the default configurations of your project. The naming convention for the dependencies items of custom configurations is Project Name Configuration Dependencies.
You can drag and drop folders within the Installation Files & Directories browser to quickly reorganize your installation file structure.
Red text indicates that a file cannot be found. If a directory appears in red text, the directory contains a missing file within it. If you see this, it is likely that a file or directory on disk was moved, renamed, or deleted. In the case of a project output group, it may indicate that the project has not yet been built in release configuration. You can use the Source Path option in the Installation File Options dialog box to view the expected path of the file. If a file you have added to the Installation Files & Directories browser has been moved on disk, you must remove the file from the browser and add it from its new path. Press <F5> to refresh the view if files have moved on disk while the Edit Installer dialog box has been open. The installer build fails if LabWindows/CVI cannot find one or more of the included files. LabWindows/CVI prompts you to build the necessary project output files when you begin the installer build, so it is not necessary to locate project output files that appear in red text in the Files tab when you edit the installer.
You can use context menus in each of the trees in the Files tab to organize and search the specified tree and modify what files are installed in what locations. The following items are available in the folders tree in the Installation Files & Directories browser. The menu items that are available depend on what folder is currently selected.
|Location||Description||Typical Directory Path on Windows|
|[Program Files]||The Program Files folder.||C:\Program Files|
|[Program Files (x86)]||The Program Files folder for 32-bit applications.
|Windows 10/8.1/7/Server 2012/Server 2008 (64-bit) C:\Windows\Program Files (x86)|
|[Desktop]||The Desktop folder (all users). Files installed here appear on every user's Windows desktop.||C:\Users\Public\Public Desktop|
|[Windows Volume]||The root directory of the partition containing the currently running Microsoft Windows installation.||C:\|
|[Windows]||The Windows folder.||C:\Windows|
|[System]||The System folder.||C:\Windows\System32|
|[SysWOW64]||The Windows on Windows 64 folder.
|Windows 10/8.1/7/Server 2012/Server 2008 (64-bit) C:\Windows\SysWOW64|
|[System16]||The folder for 16-bit system DLLs.
|[Program Data]||The Program Data or Application Data folder.||C:\ProgramData|
|[Public Documents]||The Documents folder available to all users.||C:\Users\Public\Public Documents|
|[Common Files]||The Common Files folder.||C:\Program Files\Common Files|
|[Common Files (x86)]||The Common Files folder for 32-bit applications.
|Windows 10/8.1/7/Server 2012/Server 2008 (64-bit) C:\Program Files (x86)\Common Files|
|[Start»Programs]||The Program Menu folder (all users). Files installed here appear in every user's Windows Start»Programs menu. Applications commonly install shortcuts in this directory.||C:\ProgramData\Microsoft\Windows\Start Menu\Programs|
|[Start Menu]||The Start Menu folder (all users). Systems using the Windows-XP-style Start menu display the contents at the top of the Start»Programs menu.||C:\ProgramData\Microsoft\Windows\Start Menu|
|[Startup]||The Startup folder (all users). Files installed here are run whenever any user starts a Windows session.||C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup|
|[Temp]||The current user's Temp folder.||C:\Users\[Logon User]\AppData\Local\Temp|
|[Favorites]||The current user's Favorites folder.||C:\Users\[Logon User]\Favorites|
|[Fonts]||The system Fonts folder.||C:\Windows\Fonts|
|[Templates]||The Templates folder (all users).||C:\ProgramData\Microsoft\Windows\Templates|
|[Send To]||The current user's SendTo folder. Shortcuts installed in this folder appear in the Send To menu that appears when a file is right-clicked.||C:\Users\[Logon User]\AppData\Roaming\Microsoft\Windows\SendTo|
|[National Instruments]||The directory into which National Instruments installs software. The user can change this folder at the time of installation.||C:\Program Files\National Instruments|
|[National Instruments (x86)]||The directory into which National Instruments installs 32-bit software. The user can change this folder at the time of installation.
|Windows 10/8.1/7/Server 2012/Server 2008 (64-bit) C:\Program Files (x86)\National Instruments|
|[LabVIEW]||The directory containing the highest installed version of LabVIEW. If LabVIEW is not installed on the system, the installer uses a default directory.||C:\Program Files\National Instruments\LabVIEW|
|[CVI]||The directory containing the highest installed version LabWindows/CVI. If LabWindows/CVI is not installed on the system, the installer uses a default directory.||C:\Program Files\National Instruments\CVI|
|[CVI Shared]||The LabWindows/CVI shared installation directory, which contains files such as .lib, .fp, and .h files that you want to use from multiple versions of LabWindows/CVI.||C:\Program Files\National Instruments\Shared\CVI|
|[CVI Public Documents]||The LabWindows/CVI public documents directory, which contains files that your users can see and modify. Files that you might consider installing in this folder include example programs.||C:\Users\Public\Documents\National Instruments\CVI
|[IVI Std Root]||The IVI Standard Root directory. If IVI is not installed on the system, the installer uses a default directory.
|Windows 10/8.1/7 (32-bit) C:\Program Files\IVI
Windows 10/8.1/7/Server 2012/Server 2008 (64-bit) C:\Program Files\IVI and
C:\Program Files (x86)\IVI
|[VXI PnP]||The VXIplug&play root directory. If VXI is not installed on the system, the installer uses a default directory.||Windows 10/8.1/7 (32-bit) C:\Program Files\IVI Foundation\VISA
Windows 10/8.1/7/Server 2012/Server 2008 (64-bit) C:\Program Files\IVI Foundation\VISA and
C:\Program Files (x86)\IVI Foundation\VISA
|[VXI PnP OS]||The VXIplug&play framework directory. If VXI is not installed on the system, the installer uses a default directory.||Windows 10/8.1/7/ (32-bit) C:\Program Files\IVI Foundation\VISA\WinNT
Windows 10/8.1/7/Server 2012/Server 2008 (64-bit) C:\Program Files\IVI Foundation\VISA\Win64 and
C:\Program Files (x86)\IVI Foundation\VISA\WinNT