16,472
社区成员
发帖
与我相关
我的任务
分享在DLL中如何确定自身的文件路径，GetModuleFileName 在DLL中如何使用？
在A.exe中调用了B.dll，如何在B.dll中确定自身的文件路径，因为可能不在同一目录下。
(1)
TCHAR DllPath[MAX_PATH];
GetModuleFileName(NULL,DllPath,MAX_PATH);//只能得到调用的EXE文件的路径
(2)
HMODULE g_module = NULL;
g_module = GetModuleHandle(NULL);
GetModuleFileName(g_module,exeFullPath,MAX_PATH);//也只能得到调用的EXE文件的路径
上面两种写法都不行，下面的GetModuleFileName的hModule参数在DLL中如何设置？
DWORD GetModuleFileName(
HMODULE hModule, // handle to module to find filename for
LPTSTR lpFilename, // pointer to buffer to receive module path
DWORD nSize // size of buffer, in characters
);
(1)
TCHAR DllPath[MAX_PATH];
GetModuleFileName(NULL,DllPath,MAX_PATH);//只能得到调用的EXE文件的路径
(2)
HMODULE g_module = NULL;
g_module = GetModuleHandle(NULL);
GetModuleFileName(g_module,exeFullPath,MAX_PATH);//也只能得到调用的EXE文件的路径
上面两种写法都不行，下面的GetModuleFileName的hModule参数在DLL中如何设置？
DWORD GetModuleFileName(
HMODULE hModule, // handle to module to find filename for
LPTSTR lpFilename, // pointer to buffer to receive module path
DWORD nSize // size of buffer, in characters
);
...全文
请发表友善的回复…
发表回复
Bob2000 2003-08-10
- 打赏
- 举报
非常感谢approach()的帮助，问题已经解决，送分!
an_bachelor 2003-08-10
- 打赏
- 举报
_getcwd()呢？
approach 2003-08-10
- 打赏
- 举报
Most DLL developers have faced the challenge of detecting a HMODULE/HINSTANCE handle within the module you're running in. It may be a difficult task if you wrote the DLL without a DLLMain() function or you are unaware of its name. For example:
Your DLL was built without ATL/MFC, so the DLLMain() function exists, but it's hidden from you code and you cannot access the hinstDLL parameter. You do not know the DLL's real file name because it could be renamed by everyone, so GetModuleHandle() is not for you.
This small code can help you solve this problem:
#if _MSC_VER >= 1300 // for VC 7.0
// from ATL 7.0 sources
#ifndef _delayimp_h
extern "C" IMAGE_DOS_HEADER __ImageBase;
#endif
#endif
HMODULE GetCurrentModule()
{
#if _MSC_VER < 1300 // earlier than .NET compiler (VC 6.0)
// Here's a trick that will get you the handle of the module
// you're running in without any a-priori knowledge:
// http://www.dotnet247.com/247reference/msgs/13/65259.aspx
MEMORY_BASIC_INFORMATION mbi;
static int dummy;
VirtualQuery( &dummy, &mbi, sizeof(mbi) );
return reinterpret_cast<HMODULE>(mbi.AllocationBase);
#else // VC 7.0
// from ATL 7.0 sources
return reinterpret_cast<HMODULE>(&__ImageBase);
#endif
}
Your DLL was built without ATL/MFC, so the DLLMain() function exists, but it's hidden from you code and you cannot access the hinstDLL parameter. You do not know the DLL's real file name because it could be renamed by everyone, so GetModuleHandle() is not for you.
This small code can help you solve this problem:
#if _MSC_VER >= 1300 // for VC 7.0
// from ATL 7.0 sources
#ifndef _delayimp_h
extern "C" IMAGE_DOS_HEADER __ImageBase;
#endif
#endif
HMODULE GetCurrentModule()
{
#if _MSC_VER < 1300 // earlier than .NET compiler (VC 6.0)
// Here's a trick that will get you the handle of the module
// you're running in without any a-priori knowledge:
// http://www.dotnet247.com/247reference/msgs/13/65259.aspx
MEMORY_BASIC_INFORMATION mbi;
static int dummy;
VirtualQuery( &dummy, &mbi, sizeof(mbi) );
return reinterpret_cast<HMODULE>(mbi.AllocationBase);
#else // VC 7.0
// from ATL 7.0 sources
return reinterpret_cast<HMODULE>(&__ImageBase);
#endif
}
Bob2000 2003-08-10
- 打赏
- 举报
up
Bob2000 2003-08-10
- 打赏
- 举报
to approach: GetCurrentDirectory()也只能返回调用的EXE文件的路径。
Bob2000 2003-08-10
- 打赏
- 举报
to skyhearty(天心舟): 我这个是MFC的DLL，所以没有DllMain函数。
approach 2003-08-10
- 打赏
- 举报
GetCurrentDirectory()
try it
try it
skyhearty 2003-08-10
- 打赏
- 举报
就是
BOOL APIENTRY DllMain(
HANDLE hModule,
DWORD ul_reason_for_call,
LPVOID lpReserved
)
{
return TRUE;
}
中的HANDLE hModule
BOOL APIENTRY DllMain(
HANDLE hModule,
DWORD ul_reason_for_call,
LPVOID lpReserved
)
{
return TRUE;
}
中的HANDLE hModule
skyhearty 2003-08-10
- 打赏
- 举报
在那个DLL入口有个HMODULE，用这个来传进去就可以找到了
