KnowledgeBase Archive

An Archive of Early Microsoft KnowledgeBase Articles

View on GitHub

Q59385: Incomplete EXPORTS List May Cause L2022 and L2029

Article: Q59385
Product(s): See article
Version(s): 3.65
Operating System(s): MS-DOS
Keyword(s): ENDUSER | | mspl13_basic
Last Modified: 12-MAR-1990

Compiling and linking a Windows program and receiving the following
two link errors can be caused by an incomplete EXPORTS list:

   LINK : error L2022: ProcedureName : export undefined
   LINK : error L2029: 'ProcedureName' : unresolved external

Windows programming involves the creation of a .DEF (definitions)
file. All Windows procedures to be exported must be listed in this
file. The following is an example:

   EXPORTS     ProcedureName

When this list is incomplete, the L2022 error is generated. The L2029
error can be generated if the case of the EXPORT line doesn't match
the case of the actual function.

Listing all procedures to be exported in the .DEF file prevents both
of these errors.

Note: These errors can also occur with Presentation Manager programs
or programs that use DLLs under OS/2.

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.