Missing external function dll

[flyingdc]

Hello,

I have a problem with .dll funciton. I built a .dll by myself with visual studio. I built a .vi to accee this .dll file and it works fine in my computer. However, it went wrong when I built it as an application and used it in another computer. 

In other conputer, the .vi became blocked .vi (something wrong, cannot execute) and it showed the message with "Missing external function .dll:function()......"

[altenbach]

Obviously you either did not include the dll in the build or it is in a place where the application cannot find it.

Did you build an installer or just an executable? If you only build an executable, there might be a new folder named "data" that you should keep next to the exe.

[flyingdc · Accepted solution]

Yes, i've included it and i could find the .dll file in the data folder. 

But, we found the solution of the problem. 

The .dll file we compiled is not for release use, so it's totally the problem of the .dll file. 

Then, we re-compiled the .dll file as release version and it works. 

Thank you.

[rolfk]

And you may also have to install the according C Runtime Library for the Visual C version you used to create the DLL. 

Visual Studio.2003 until 2015 all use their version specific C Runtime Library which may or may not be installed on a specific computer. If depends on the Windows version and other already installed application on that computer that may install a specific runtime version for themselves

Since 2015 the Visual C Runtime remained at the same major version number (14.x) and shared library name so it should be always present on a Windows 10 computer but you should still be prepared to install the C Runtime Library if you use the greatest and latest Visual C version since the runtime is upwards compatible but not backwards. For instance, if you create an executable or DLL in Visual Studio 2022 (Version 17.2)  but the target computer doesn’t have the matching C Runtime 14.32 or higher installed you still can get an unloadable DLL or strange failures, due to missing runtime exports that your DLL may be linked with.

[flyingdc]

OK, Thank you