Mass compiling your VIs in LabVIEW 2013 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.
a. Mass Compile Your VIs in the New Version of LabVIEW
Mass compiling VIs simultaneously converts and saves the VIs in LabVIEW 2013. 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.
b. Fix Any Broken VIs
Improvements between your previous version of LabVIEW and LabVIEW 2013 can occasionally cause some VIs to break if they use outdated features. To quickly identify and fix broken VIs in LabVIEW 2013, complete the following steps:
- 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.
- To determine whether updates to LabVIEW caused each VI to break, refer to the section of the Upgrade and Compatibility Issues topic for each version of LabVIEW between your previous version and LabVIEW 2013.
c. Identify and Correct Behavior Changes
Although National Instruments 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:
- Upgrade VI Analyzer Tests—For large sets of VIs, these tests provide an efficient way to identify many behavior changes caused by upgrading. Complete the following steps to obtain and use these tests:
- Download the Upgrade VI Analyzer Tests for all versions of LabVIEW later than your previous version from the National Instruments website at ni.com.
- Open and run the tests by selecting Tools»VI Analyzer»Analyze VIs and starting a new VI Analyzer task. To analyze an entire project at once, select this menu option from the Project Explorer window rather than from a single VI.
- Resolve test failures by referring to the Upgrade and Compatibility Issues section for the version of LabVIEW that corresponds to the tests. For example, if the LabVIEW 2010 Upgrade VI Analyzer tests locate a potential behavior change, refer to the Upgrading from LabVIEW 2009 section of that topic.
- Upgrade documentation
- Upgrade and Compatibility Issues topic—Lists changes that may break or affect the behavior of your VIs. Refer to the subsections for each version of LabVIEW beginning with your previous version.
||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.
- LabVIEW 2013 Known Issues list—Lists bugs discovered before and throughout the release of LabVIEW 2013. Refer to the Upgrade - Behavior Change and Upgrade - Migration sections to identify workarounds for any bugs that may affect the behavior of upgraded VIs.
- Module and toolkit documentation—For some modules and toolkits, such as LabVIEW FPGA and the LabVIEW Real-Time Module, lists upgrade issues specific to that add-on
- Driver readme files—Lists upgrade issues specific to each driver. To locate each readme, refer to the installation media for the driver.
||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 2013.
- Your own tests—Perform the same tests on the VIs in LabVIEW 2013 that you performed in the previous version and compare the results. If you identify new behaviors, refer to the upgrade documentation to diagnose the source of the change.