Re: Issues with Porting VS6.0 MFC Projects to VS8.0 - Need Help
- From: "Carl Daniel [VC++ MVP]" <cpdaniel_remove_this_and_nospam@xxxxxxxxxxxxxxx>
- Date: Fri, 4 Aug 2006 14:15:24 -0700
"BK-Chicago" <BKChicago@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:895803B7-C2C0-477C-AADF-B6CDE1214A29@xxxxxxxxxxxxxxxx
I am in the midst of porting a massive MFC application from VS6.0 to VS8.0.
While i have fixed most of the compile time errors, i do have quite a
linker
error that i have not been able to resolve. The error i get is
Error 100 error LNK2001: unresolved external symbol "public: virtual void
__thiscall CWnd::PostNcDestroy(void)"
(?PostNcDestroy@CWnd@@UAEXXZ) Evenout.obj
I have about 200 of these on almost all the obj's that have a dialog in
them(which is understandable). But i do see that the delcaration of
CWnd::PostNcDestory( ) in the systems afxwin.h header which is public:
// for custom cleanup after WM_NCDESTROY
public:
virtual void PostNcDestroy();
Do i need to refer to any particular version of SDK/ *.lib or am i
missing
something. Any help here would be appreciated.
Make sure that you're not still linking against the VC6 version of MFC.
Check the project settings and the Tools|Options|Projects and Solutions|C++
Directories to make sure that the VS2005 directories are the only ones on
the library search path.
-cd
.
- Follow-Ups:
- Re: Issues with Porting VS6.0 MFC Projects to VS8.0 - Need Help
- From: BK-Chicago
- Re: Issues with Porting VS6.0 MFC Projects to VS8.0 - Need Help
- Prev by Date: Re: [out] attribute doesn't seem to work on static methods
- Next by Date: Re: Issues with Porting VS6.0 MFC Projects to VS8.0 - Need Help
- Previous by thread: [out] attribute doesn't seem to work on static methods
- Next by thread: Re: Issues with Porting VS6.0 MFC Projects to VS8.0 - Need Help
- Index(es):