Table Of Contents

Preparing Your LabVIEW Code for Conversion to LabVIEW NXG

Last Modified: September 28, 2017

Before generating new code using the Code Conversion Utility, prepare the existing source code to reduce the amount of clean-up required in the converted code.


You do not need to manually copy or move the source files on disk prior to converting. The Code Conversion Utility does not modify the original source files.

  1. Open the source code using a supported version of LabVIEW, ensure all dependencies are present, and save the source code. LabVIEW reports a dependency error when attempting to open a project with missing dependencies.

    Any missing dependencies in the source code from the original LabVIEW product will be replaced by empty placeholder nodes in the converted LabVIEW NXG source code.

  2. If you have never run the code you want to convert on the machine you are using for conversion, mass compile the VIs in your existing project to resolve any broken links caused by stale cache files.

After preparing the existing source code, convert your code using the Code Conversion Utility.

The following table notes differences to be aware of before converting your content:

Topic LabVIEW LabVIEW NXG What to Do
File Extensions .vi .gvi Review hard-coded file paths before running migrated code.
Item Naming Allows unnamed or non-uniquely named items such as controls All item names must be non-empty and unique. Review changed item names after migration.
Node Style Guidelines Error terminals placed at bottom row of icon Error terminals placed at 2nd row of icon Review icon connections of migrated VI's

Recently Viewed Topics