In the first part of this series we saw the problems involved with using DLLs in an environment different from the one in which they were developed. In this part we will learn more about resolving some of these problems.
DLL Conventions: Issues and Solutions - Part II - How to identify exported symbols (Page 2 of 4 )
You can use any tool that dumps information about a DLL import/export, such as tdump from Borland, or Dependency Walker (which comes bundled with Visual Studio). I use Depends.exe most of the time; I used it to view the exports from the MSVC as well as the BCB DLL. Below are the screen shots for the same. Figure 1 shows the exports for the DLL built with Borland C++ builder and Figure 2 shows the exports for the DLL built with Visual C++ Compiler.
Fig 1: Exports from the BCB built DemoDLL.dll
Fig 2: Exports from the MSVC built DemoDLL.dll
In order to see the true linker names you should turn the undecorated feature to off, as shown in Figure 3.
Fig 3: Turn undercoating OFF in order to view true linker names