|LabVIEW 2016 Help|
|LabVIEW 2017 Help|
|LabVIEW 2018 Help|
|LabVIEW 2019 Help|
|LabVIEW 2020 Help|
Mass compiling your VIs in LabVIEW 2018 converts the VIs to the new version of LabVIEW and creates an error log to help you identify VIs that are broken. You can use this information in conjunction with the Upgrade and Compatibility Issues topic to identify and correct behavior changes associated with the new version of LabVIEW.
|Note If you mass compiled your VIs when you upgraded to LabVIEW 2017, you can skip this step because LabVIEW 2017 and later supports backward compatibility for the LabVIEW Run-Time Engine.|
Mass compiling VIs simultaneously converts and saves the VIs in LabVIEW 2018. However, after mass compiling 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. Therefore, mass compile only the VIs that you want to convert to the new version of LabVIEW. 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.
|Note 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 your previous version of LabVIEW and LabVIEW 2018 can occasionally cause some VIs to break if they use modified features. To quickly identify and fix broken VIs in LabVIEW 2018, complete the following steps:
Although NI invests significant effort to avoid changing the behavior of VIs between different versions of LabVIEW, improvements and bug fixes occasionally do alter the behavior of VIs. To quickly identify whether the new version of LabVIEW changes the behavior of your VIs, use one or more of the following tools:
|Tip To quickly locate deprecated objects and other objects mentioned in the Upgrade and Compatibility Issues topic, open your upgraded VIs and select Edit»Find and Replace.|
|Tip To determine whether a behavior change resulted from a driver update rather than an update to LabVIEW, test your VIs in the previous version of LabVIEW after installing LabVIEW 2018.|
|Previous: Install LabVIEW, Add-Ons, and Device Drivers||Next: Troubleshooting Common Upgrade Issues|