Important:
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
A version of this page is also available for
4/8/2010

This function returns the address of the specified exported DLL function.

Syntax 

FARPROC GetProcAddress(
  HMODULE 
hModule,
  LPCWSTR 
lpProcName
);

Parameters

hModule

[in] Handle to the DLL module that contains the function.

The LoadLibraryor the GetModuleHandlefunction returns this handle.

lpProcName

[in] Pointer to a null-terminated string containing the function name, or specifies the function's ordinal value.

If this parameter is an ordinal value, it must be in the low-order word; the high-order word must be zero.

This parameter must be in Unicode.

Return Value

The address of the DLL's exported function indicates success. NULL indicates failure. To get extended error information, call GetLastError.

Remarks

For Windows CE 3.0 and later, the ASCII version of this function, GetProcAddressA, is supported. With this version, lpProcNameis of the type LPCSTR.

The GetProcAddressfunction is used to retrieve addresses of exported functions in DLLs.

The spelling and case of the function name pointed to by lpProcNamemust be identical to that in the EXPORTSstatement of the source DLL's module-definition (.def) file.

The exported names of Win32 APIs might differ from the names you use when calling these functions in your code. This difference is hidden by macros used in the SDK header files.

The lpProcNameparameter can identify the DLL function by specifying an ordinal value associated with the function in the EXPORTSstatement.

GetProcAddressverifies that the specified ordinal is in the range 1 through the highest ordinal value exported in the .def file.

The function then uses the ordinal as an index to read the function's address from a function table.

If the .def file does not number the functions consecutively from 1 to N(where Nis the number of exported functions), an error can occur where GetProcAddressreturns an invalid, nonnull address, even though there is no function with the specified ordinal.

In cases where the function might not exist, the function should be specified by name rather than by ordinal value.

When using GetProcAddressto obtain the address of the InitSecurityInterfacefunction, use SECURITY_ENTRYPOINT for lpProcName.

Requirements

Header winbase.h
Library coredll.lib
Windows Embedded CE Windows CE 1.0 and later
Windows Mobile Windows Mobile Version 5.0 and later

See Also