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.

Archived:Migrating LabVIEW Old Source Code to LabVIEW NXG

Updated Apr 14, 2023

NI does not actively maintain this document.

This content provides support for older products and technology, so you may notice outdated links or obsolete information about operating systems or other relevant products.

Reported In

Software

  • LabVIEW
  • LabVIEW NXG

Other

  • Code Conversion Utility for LabVIEW NXG

Issue Details

Is it possible to migrate my LabVIEW VIs or projects to LabVIEW NXG?

Solution

Note: The final release of LabVIEW NXG was LabVIEW NXG 5.1 in 2021. LabVIEW NXG is not recommended for new projects. For more information about the change in the LabVIEW NXG life cycle, refer to the announcement in the LabVIEW Forum.
 

Yes, it is possible to migrate LabVIEW Source Code to LabVIEW NXG, with the help of the Code Conversion Utility, which is included in LabVIEW NXG. Follow Guidance in the LabVIEW NXG Help on Converting LabVIEW Code with the Code Conversion Utility to Use in LabVIEW NXG.

Before beginning, read through how to prepare your LabVIEW Code for Conversion to LabVIEW NXG.

 

Considerations

Before converting a whole application, realize that not all features are supported in LabVIEW NXG, and LabVIEW NXG will no longer be supported by NI technical support as of July 15, 2022.

For small applications, the Code Conversion Utility will produce a close representation of the LabVIEW code. For medium to large size applications, the complexity of conversion and cleanup increases, and you should evaluate what parts of your application to convert and which to keep in LabVIEW.

Additional Information

  • After conversion completes, and you have reviewed the report, you can start to resolve the conversion messages. The conversion report provides several ways to organize messages so they can be resolved in a way that makes sense for your project. For most cases, it will be beneficial to start by focusing on messages which require a manual fix. Click on a message in the conversion report to navigate to its location in the code.
    • Most scenarios, other than those involving simple applications, will require a time investment to resolve conversion messages and return the code to a working state. The amount of time required to resolve the messages varies widely depending on the complexity of the code. Smaller sets of codes (less than 50 VIs) should require a few hours, while larger code sets may require significantly more time to resolve the entirety of the conversion messages.
  • If you are considering migrating a Vision application to LabVIEW NXG refer to the document Frequently Asked Questions about Vision NXG .