Table Of Contents


Last Modified: February 27, 2020

The Code Conversion Utility replaced a Call Library Function Node with a placeholder node. This version of LabVIEW NXG does not support Call Library Function Nodes that call DLLs or shared libraries using the path in input.

If your application uses a Call Library Function Node where you specified your path to a DLL instead of using the path in input, LabVIEW NXG converts the Call Library Function Node to an SLI. This version of LabVIEW NXG does not support DLLs being dynamically loaded using the path in input. Performance implications may occur because the DLL can no longer be dynamically loaded or unloaded.

What to Do

If your shared library is widely used in your application, consider updating the Call Library Function Node in LabVIEW to statically reference the DLL and then reconvert your application to LabVIEW NXG. Making this change and reconverting your application automatically generates the SLI document and correctly replaces all the Call Library Function Nodes with SLI calls. If you use your library sparingly, you can create an SLI document for the DLL and replace the placeholder with an SLI call. Creating an SLI document does not require reconverting.

Alternate Workarounds

If the previous suggestions don't restore the functionality of the affected code and the code isn't essential to the core functionality of your application, you can remove the portion of code. If the code is part of the core functionality of the application, you can use the VI Interop node to call your existing code, provided that the new code organization meets the architectural goals of your application. If neither solution meets the requirements of your application, do not migrate to LabVIEW NXG at this time.

Recently Viewed Topics