Calling an Exported Function in an EXE from Within a DLL

Environment: VC6, SP4, 2K, SP2

This article explains a better way of calling a function in an EXE file from a dependent DLL of the same EXE. In other words, calling a DLL's function from an EXE is the normal way; this is the reverse of the same.

On CodeGuru I have found a couple of FAQs talking about the same issue. They tell you to have a call back function to hold the pointer from the EXE and so on, but they look primitive. In this article, I have given a better method of calling functions from the EXE. I would be glad if this helps someone in need.

In the EXE:

// Do exactly as you would export a DLL...
extern "C"
  EXPORT void ExeFn(char * lpszMessage)
    MessageBox(NULL,lpszMessage,"From Exe",MB_OK);

In the DLL:

// Get the handle of the EXE that loaded us.

FnPtrT FnPtr = (FnPtrT)::GetProcAddress(GetModuleHandle(NULL),
  (*FnPtr)("Message From The DLL");
  MessageBox(NULL,"It Did Not work :(","From DLL",MB_OK);



Note: In this demo project, I have just implemented the above-mentioned exports. The EXE calls the DLL's function and that function calls a function in the EXE. Those functions do nothing more than display message boxes, so there's no point in giving a demo EXE. Just build the source; you must get the DLL and EXE.

How to Build It

  • Extract the source zip file. Open workspace "ExportingExe.dsw".
  • Ensure that ExportingExe is the active project. Now, you can build and run it.
  • Because Importing.DLL is a dependency of the other one, you don't have to bother about anything else.
Download source - 16 Kb


  • There are no comments yet. Be the first to comment!

Leave a Comment
  • Your email address will not be published. All fields are required.

Top White Papers and Webcasts

  • Anthony Christie, the Chief Marketing Officer for Level Communications, is responsible for customer experience, worldwide marketing and product management. In this informative asset, he shares his insights into why a private network connection to cloud-bases applications is the right decision for your enterprise. Download now to find out more.

  • Moving from an on-premises environment to Office 365 does not remove the need to plan for disruptions or reduce the business risk requirements for protecting email services. If anything, some risks increase with a move to the cloud. Read how to ease the transition every business faces if considering or already migrating to cloud email. This white paper discusses: Setting expectations when migrating to Office 365 Understanding the implications of relying solely on Exchange Online security Necessary archiving …

Most Popular Programming Stories

More for Developers

RSS Feeds

Thanks for your registration, follow us on our social networks to keep up-to-date