帮我解释一下这个函数及参数DllEntryPoint???

[yulei0707]

BOOL WINAPI DllEntryPoint(

HINSTANCE hinstDLL, // handle to DLL module
DWORD fdwReason, // reason for calling function
LPVOID lpvReserved // reserved
);


Parameters

hinstDLL

A handle to the DLL. The value is the base address of the DLL. The HINSTANCE of a DLL is the same as the HMODULE of the DLL, so hinstDLL can be used in subsequent calls to the
GetModuleFileName function and other functions that require a module handle.

fdwReason

Specifies a flag indicating why the DLL entry-point function is being called. This parameter can be one of the following values:

Value Meaning
DLL_PROCESS_ATTACH
Indicates that the DLL is attaching to the address space of the current process as a result of the process starting up or as a result of a call to LoadLibrary. DLLs can use this opportunity to initialize any instance data or to use the TlsAlloc function to allocate a thread local storage (TLS) index.
During initial process startup or after a call to LoadLibrary, the operating system scans the list of loaded DLLs for the process. For each DLL that has not already been called with the DLL_PROCESS_ATTACH value, the system calls the DLL's entry-point function. This call is made in the context of the thread that caused the process address space to change, such as the primary thread of the process or the thread that called LoadLibrary.
DLL_THREAD_ATTACH
Indicates that the current process is creating a new thread. When this occurs, the system calls the entry-point function of all DLLs currently attached to the process. The call is made in the context of the new thread. DLLs can use this opportunity to initialize a TLS slot for the thread. A thread calling the DLL entry-point function with the DLL_PROCESS_ATTACH value does not call the DLL entry-point function with the DLL_THREAD_ATTACH value.
Note that a DLL's entry-point function is called with this value only by threads created after the DLL is attached to the process. When a DLL is attached by LoadLibrary, existing threads do not call the entry-point function of the newly loaded DLL.
DLL_THREAD_DETACH
Indicates that a thread is exiting cleanly. If the DLL has stored a pointer to allocated memory in a TLS slot, it uses this opportunity to free the memory. The operating system calls the entry-point function of all currently loaded DLLs with this value. The call is made in the context of the exiting thread. There are cases in which the entry-point function is called for a terminating thread even if the DLL never attached to the thread ?for example, the entry-point function was never called with the DLL_THREAD_ATTACH value in the context of the thread in either of these two situations:?The thread was the initial thread in the process, so the system called the entry-point function with the DLL_PROCESS_ATTACH value. ?The thread was already running when a call to the LoadLibrary function was made, so the system never called the entry-point function for it.


DLL_PROCESS_DETACH
Indicates that the DLL is detaching from the address space of the calling process as a result of either a clean process exit or of a call to FreeLibrary. The DLL can use this opportunity to call the TlsFree function to free any TLS indices allocated by using TlsAlloc and to free any thread local data. When a DLL detaches from a process as a result of process termination or as a result of a call to FreeLibrary, the operating system does not call the DLL's entry-point function with the DLL_THREAD_DETACH value for the individual threads of the process. The DLL is only given DLL_PROCESS_DETACH notification. DLLs can take this opportunity to clean up all resources for all threads attached and known to the DLL.


lpvReserved

Specifies further aspects of DLL initialization and cleanup.
If fdwReason is DLL_PROCESS_ATTACH, lpvReserved is NULL for dynamic loads and non-NULL for static loads.
If fdwReason is DLL_PROCESS_DETACH, lpvReserved is NULL if DllEntryPoint has been called by using FreeLibrary and non-NULL if DllEntryPoint has been called during process termination.

[KingOf007]

这段英语还是挺简单的,为了100分,我给你翻译一下吧

[KingOf007]

靠,看能看懂,翻译起来倒挺麻烦的,简单点说就是:
hinstDLL是动态链接库的基址,可以在调用一些API函数时用到,
reason就是操作系统对此DLL的操作:
DLL_PROCESS_ATTACH:是作为一个进程加载
DLL_PROCESS_DETACH:是进程卸载此DLL
DLL_THREAD_ATTACH:是作为一个线程加载
DLL_THREAD_DETACH:是作为线程加载后的卸载
最后一个参数:是在进程加载或卸载时,传入的一个参数
如果是动态加载,则为NULL,如果是静态加载,则为非空
如果是调用FreeLibrary来卸载,此值为NULL,如果是随进程一起结束,为非NULL

[KingOf007]

而这个函数呢,是由操作系统调用,为了在加载或卸载时,作一些处理用的

[yulei0707]

还是不太清楚能不能详细一点

[kingfish]

推荐你看《windows核心编程》第20章

[SuperSuperLéon]

DllEntryPoint 是 标准C 下的

动态库入口函数。

你在使用中，参照DllMain就可以了。

除非你有特殊应用，否则，不用理会得太深。

[SuperSuperLéon]

你看这个：

BOOL WINAPI DllMain(
HINSTANCE hinstDLL, // handle to the DLL module
DWORD fdwReason, // reason for calling function
LPVOID lpvReserved // reserved
);

这个和下面的是一个。

BOOL WINAPI DllEntryPoint(

HINSTANCE hinstDLL, // handle to DLL module
DWORD fdwReason, // reason for calling function
LPVOID lpvReserved // reserved
);

呵呵。


因此，DllMain 和DllEntryPoint 是一回事，只不过DllEntryPoint是老版本的。

更好的E 文资料见 .net Msdn.

关于 DllMain 的具体说法你去看：

《新编 Windows Api 参考大全》P489。这里写的很详细。

不过有两句关于 DllMain 的 翻译得不够准确。

我要是把它打上来，也太那个了。



ok?

啊，哈欠，我困了，我睡了。bye.

[bobZ]

DLL入口点函数，reason值是系统传递的参数，当此DLL第一次被进程装载时reason值为DLL_PROCESS_ATTATCH,DLL最终被卸载时，reason值为DLL_PROCESS_DETATCH.

[invalid]

int WINAPI DllEntryPoint(HINSTANCE hinst, unsigned long reason, void* lpReserved)
{
switch (reason)
{
case DLL_PROCESS_ATTACH:
if(lpReserved)
OutputDebugString("DLL_PROCESS_ATTACH Static load");
else
OutputDebugString("DLL_PROCESS_ATTACH Dynamic load");
GetModuleFileName(hinst,dllpath,255);
break;
case DLL_PROCESS_DETACH:
if(lpReserved)
OutputDebugString("DLL_PROCESS_DETACH Call process termination!");
else
OutputDebugString("DLL_PROCESS_DETACH FreeLibrary");
break;
case DLL_THREAD_ATTACH:
OutputDebugString("DLL_THREAD_ATTACH");
break;
case DLL_THREAD_DETACH:
OutputDebugString("DLL_THREAD_DETACH");
break;
default:
OutputDebugString("DllEntryPoint");
}
return 1;

[gk0205]

好东西