🚀 go-pugleaf

Andrue Cope [TeamB] wrote:

>Kathleen Beaumont wrote:
>
>> PROBLEM: My implementation of DllEntryPoint does not get accessed.

>Same here.
>In our case DLLEntryPoint doesn't do anything anyway (it's an old DLL
>and we export our own Init() and Done() functions but I did wonder
>about it the other day.

Maybe they need to be named DllMain ?

From BCB help:
"DllEntryPoint is a placeholder for the library-defined function name.
The actual name must be specified at build time. For more information,
see the documentation included with your development tools."

From MSDN:
"To initialize non-MFC DLLs, your DLL source code must contain a
function called DllMain. The following code presents a basic skeleton
showing what the definition of DllMain might look like:
{code}
Note   The Platform SDK documentation for DllEntryPoint says that the
actual name of the entry-point function must be specified on the
linker command line with the /ENTRY option. With Visual C++, you do
not need to use the /ENTRY option if the name of your entry-point
function is DllMain. In fact, if you do use the /ENTRY option and name
your entry-point function something other than DllMain, the C run-time
library will not get initialized properly."

Andrue, is there some reason you don't just remove the (default)
startup code? According to this it is optional.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dllproc/base/dynamic_link_library_entry_point_function.asp
"A DLL can optionally specify an entry-point function"