microsoft visual studio 2017 how to make a function

#MICROSOFT VISUAL STUDIO 2017 HOW TO MAKE A FUNCTION WINDOWS 10#
#MICROSOFT VISUAL STUDIO 2017 HOW TO MAKE A FUNCTION WINDOWS#

Simply check the checkbox in the Call Library Node configuration function to pass the library name from the diagram. LoadLibrary() is an expensive function and calling it each time the Call Library Node gets executed would be a waste of performance. Unless you use the option to specify the Library path on the diagram and pass it to the node, LabVIEW will LoadLibrary() the specified library at time of loading the VI that contains the Call Library Node and simply invoke the function at runtime. When LoadLibrary() fails, LabVIEW simply informs you that it could not load the function XYX from the DLL, without trying to guess if the function itself is not present. In order for LabVIEW to link to a DLL for execution of the functions it does need to use the normal LoadLibrary() function and that function fails when any of the dependencies can not be resolved. The Get DLL Exports.vi function only walks the export table in the DLL and lists all entries using LoadLibraryEx(path, LOAD_LIBRARY_AS_DATAFILE)., it does NOT attempt to load the library for execution using normal LoadLibrary(). That error message is unfortunately not very specific as to the error why it can't reference the function.

#MICROSOFT VISUAL STUDIO 2017 HOW TO MAKE A FUNCTION WINDOWS#

Why would recompiling the DLL in Visual Studio 2017 vs 2013 change how LabView sees the available functions from within Windows XP?Īnyone else encountered anything like this or have a potential solution? Why would the same version of the DLL and same version of LabView work just fine in Windows 10, but have 'Function not found in library' errors in Windows XP?

When I go back to a version of the DLL compiled in Visual Studio 2013, there are no errors in Windows XP anymore.

DepencyWalker does not show any missing decencies for the DLL.

The LabView 'Display Exported Functions' tool clearly reports the function names are visible to LabView in both Windows XP and Windows 10.

The EXE's that also rely on the DLL run without errors under both Windows XP and Windows 10, so the DLL entry points are not incompatible with the operating systems.

#MICROSOFT VISUAL STUDIO 2017 HOW TO MAKE A FUNCTION WINDOWS 10#

The same VI's run perfectly fine with this new version of the DLL on newer Windows 10 test machines (also running LabView 6), so the exporting of functions from the DLL is still correct.

The errors only occur when running our test VI's on older Windows XP machines.

I have just completed the process of updating the DLL to continue development in Visual Studio 2017 and have encountered 'Function not found in library' errors. Our test lab is still standardized on LabView 6. I have a proprietary DLL as well as supporting EXE's to manage test computer IO and automation that we have developed in-house over the last decade-and-a-half. We have been using functions from this DLL within LabView VI's for just about as long.

Microsoft visual studio 2017 how to make a function