I'm working on a project that involves writing a plugin DLL for a game, and being the lazy programmer I am, I'm using the example provided by the game author and modifying it for my needs. I don't have access to the DLL's
HINSTANCE (like we do with MFC DLLs). This presented a problem when I decided I needed to know the full path to the DLL in question.
Believe it or not, it only takes three lines of code to accomplish this task:
EXTERN_C IMAGE_DOS_HEADER __ImageBase;
LPTSTR strDLLPath1 = new TCHAR[_MAX_PATH];
::GetModuleFileName((HINSTANCE)&__ImageBase, strDLLPath1, _MAX_PATH);
It seems that any EXE or DLL compiled with the VS2002 (and higher) linkers provides a psuedo-variable called
__ImageBase that represents the DOS header of the module (all 32 bit binaries have this). Simply cast this variable to a
HINSTANCE, and you can pass it as the first parameter to
For those of you that need this functionality in VC6 or earlier, research the
VirtualQuery() function. The approach is somewhat similar.
I don't know if this will work in Vista.
The sample code includes source and the compiled EXE and DLL files.
I've been paid as a programmer since 1982 with experience in Pascal, and C++ (both self-taught), and began writing Windows programs in 1991 using Visual C++ and MFC. In the 2nd half of 2007, I started writing C# Windows Forms and ASP.Net applications, and have since done WPF, Silverlight, WCF, web services, and Windows services.
My weakest point is that my moments of clarity are too brief to hold a meaningful conversation that requires more than 30 seconds to complete. Thankfully, grunts of agreement are all that is required to conduct most discussions without committing to any particular belief system.