Home > Software engineering >  Can't locate the ordinal number 999 in the dynamic link library COREDLL. DLL
Can't locate the ordinal number 999 in the dynamic link library COREDLL. DLL

Time:10-08

I in commissioning program, transplanted into my vs2010 and XPM found lost. DLL files, I download on the net the mfc90ud. DLL in the system32 (the machine is only found in the system32 folder mfc100 and mfc110 above. DLL, don't know is what reason), then download the various such as coredll. DLL, mmvcp70. Mmvcr70. DLL, the DLL... Finally debugging success, generate the corresponding exe file, but open display: unable to locate ordinal number 999 in the dynamic link library COREDLL. DLL, and on the Internet to download the other COREDLL. DLL (but feel and is the same as before, because of time and all the same size), found after replacement is still the same, I don't know COREDLL. What's the use of DLL, why can't run?

CodePudding user response:

Using static link program,,

CodePudding user response:

reference 1st floor paschen response:
using static link program,,


What do you mean? How to use static link program?

CodePudding user response:

reference 1st floor paschen response:
using static link program,,


I changed the runtime to MT or MTD error:
2010 v d: \ \ vc \ atlmfc \ include \ afxver_ h (81) : fatal error C1189: # error: both Please use the/MD switch for _AFXDLL builds

Did not even successful compilation, can only use the MD or MDD

CodePudding user response:

reference kuanbifeng6183 reply: 3/f
Quote: refer to 1st floor paschen response:

Using static link program,,


I changed the runtime to MT or MTD error:
2010 v d: \ \ vc \ atlmfc \ include \ afxver_ h (81) : fatal error C1189: # error: both Please use the/MD switch for _AFXDLL builds

Did not even successful compilation, can only use the MD or MDD?


The project properties - - the use of MFC: conventional use MFC in a static library

CodePudding user response:

reference 4 floor paschen response:
Quote: reference kuanbifeng6183 reply: 3/f

Quote: refer to 1st floor paschen response:

Using static link program,,


I changed the runtime to MT or MTD error:
2010 v d: \ \ vc \ atlmfc \ include \ afxver_ h (81) : fatal error C1189: # error: both Please use the/MD switch for _AFXDLL builds

Did not even successful compilation, can only use the MD or MDD?


The project properties - - the use of MFC: conventional use MFC in a static library


That my own recompiling. Lib and. DLL is have to change in the static library to recompile, then loaded into the project

CodePudding user response:

reference 4 floor paschen response:
Quote: reference kuanbifeng6183 reply: 3/f

Quote: refer to 1st floor paschen response:

Using static link program,,


I changed the runtime to MT or MTD error:
2010 v d: \ \ vc \ atlmfc \ include \ afxver_ h (81) : fatal error C1189: # error: both Please use the/MD switch for _AFXDLL builds

Did not even successful compilation, can only use the MD or MDD?


The project properties - - the use of MFC: conventional use MFC in a static library



Or not, appear this error: error LNK2005: "public: static class CWnd * __stdcall CWnd: : FromHandle (struct HWND__ *)" (? FromHandle @ CWnd @ @ SGPAV1 @ PAUHWND__ @ @ @ Z) have been mfc90ud. Lib (mfc90ud. DLL) defined in the

See online answer is needed for dynamic link libraries, I carefully looked at the coredll. DLL, ready to register in the command prompt:
the mistakes

CodePudding user response:

@ 4 teacher zhao, @ paschen, @ zgl7903, teachers, solve the ~

CodePudding user response:

With the
Dumpbin. Exe/EXPORTS coredll. DLL
Command to see coredll. DLL export functions list and its export corresponding ordinal
"Windows core programming
"http://www.dllzj.com

CodePudding user response:

With the depends. Exe see the exe and DLL rely on other DLL and its version number,
In a 64 - bit Windows:
64 exe and DLL in the directory c: \ Windows \ sys tem32 directory.
32 bit exe and DLL in the directory c: \ Windows \ sys wow64 directory.
So pay attention to:
In win64 system registered under 32-bit ocx DLL to 32 ocx or copy the DLL to the c: \ Windows \ syswow64 \ directory,
And registered to c: \ Windows \ syswow64 \ regsvr32 XXXXXXX ocx or DLL
  • Related