Convert Your VIs

Mass compile your VIs in your new version of LabVIEW. You can generate an error log to help you identify VIs that are broken as a result of changes between versions.

  1. Check out your VIs from source code control.
    Source code control backs up your VIs and tracks changes. If you cannot address behavior changes caused by upgrading the VIs, you can revert to a previous version of the VIs.
    Include only VIs that you want to convert to the new version of LabVIEW. After upgrading the VIs, you no longer can open the VIs in a previous version of LabVIEW without selecting File » Save for Previous Version for each VI or project.
  2. Mass compile the VIs.
    Mass compiling VIs simultaneously converts and saves the VIs in your new version of LabVIEW.
  3. To help identify any problems that arose from upgrading, create a mass compile log by placing a checkmark in the Log Results checkbox of the Mass Compile dialog box.
  4. When you mass compile VIs that contain FPGA or real-time resources, the Mass Compile dialog box may report the VIs as non-executable VIs. To check for errors, you must open the VIs under the FPGA or RT target in a LabVIEW project with the required FPGA or real-time resources.
Differences between LabVIEW versions can occasionally cause some VIs to break if they use modified features. To quickly identify and fix broken VIs, complete the following steps:
  1. To identify VIs that broke during upgrading, compare the mass compile error log you created in the previous step to the log you created when testing the existing behavior of the VIs.
  2. To determine whether updates to LabVIEW caused each VI to break, refer to Upgrade and Compatibility Issues.