Issues with Porting VS6.0 MFC Projects to VS8.0 - Need Help

[BK-Chicago]

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::PostNcDes troy(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::PostNcDes tory( ) 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.

[Carl Daniel [VC++ MVP]]

"BK-Chicago" <BK*******@disc ussions.microso ft.comwrote in message
news:89******** *************** ***********@mic rosoft.com...

>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::PostNcDes troy(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::PostNcDes tory( ) 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|P rojects and Solutions|C++
Directories to make sure that the VS2005 directories are the only ones on
the library search path.

-cd

[BK-Chicago]

Thank you for looking into this.

This is what i have set in the Tools Option category.

<ToolsOptionsSu bCategory name="VCDirecto ries"
RegisteredName= "VCDirector ies" PackageName="Vi sual C++ Project System
Package">
<PropertyValu e
name="LibraryDi rectories">Win3 2|$(VCInstallDi r)lib;$(VCInsta llDir)atlmfc\li b;$(VCInstallDi r)atlmfc\lib\i3 86;$(VCInstallD ir)PlatformSDK\ lib;$(Framework SDKDir)lib;$(VS InstallDir);$(V SInstallDir)lib |x64|$(VCInstal lDir)lib\amd64; $(VCInstallDir) atlmfc\lib\amd6 4;$(VCInstallDi r)PlatformSDK\l ib\amd64;$(VSIn stallDir)SDK\v2 .0\lib\amd64|Po cket
PC 2003
(ARMV4)|$(VSIns tallDir)SmartDe vices\SDK\Pocke tPC2003\lib\ARM V4;$(VCInstallD ir)ce\atlmfc\li b\ARMV4;$(VCIns tallDir)ce\lib\ ARMV4;|Smartpho ne
2003
(ARMV4)|$(VSIns tallDir)SmartDe vices\SDK\Smart Phone2003\lib\A RMV4;$(VCInstal lDir)ce\atlmfc\ lib\ARMV4;$(VCI nstallDir)ce\li b\ARMV4;</PropertyValue>
<PropertyValu e
name="Reference Directories">Wi n32|$(Framework Dir)$(Framework Version);$(VCIn stallDir)atlmfc \lib|x64|$(Fram eworkDir)$(Fram eworkVersion);$ (VCInstallDir)a tlmfc\lib\amd64 |Pocket PC 2003 (ARMV4)||Smartp hone 2003 (ARMV4)|</PropertyValue>
<PropertyValu e
name="ExcludeDi rectories">Win3 2|$(VCInstallDi r)include;$(VCI nstallDir)atlmf c\include;$(VCI nstallDir)Platf ormSDK\include; $(FrameworkSDKD ir)include;$(Fr ameworkDir)$(Fr ameworkVersion) ;$(VCInstallDir )atlmfc\lib|x64 |$(VCInstallDir )include;$(VCIn stallDir)atlmfc \include;$(VCIn stallDir)Platfo rmSDK\include;$ (FrameworkSDKDi r)include;$(Fra meworkDir)$(Fra meworkVersion); $(VCInstallDir) atlmfc\lib\amd6 4|Pocket
PC 2003
(ARMV4)|$(VCIns tallDir)ce\incl ude;$(VSInstall Dir)SmartDevice s\SDK\PocketPC2 003\include;$(V CInstallDir)ce\ atlmfc\include; $(VSInstallDir) SmartDevices\SD K\SQL
Server\Mobile\v 3.0;;|Smartphon e 2003
(ARMV4)|$(VCIns tallDir)ce\incl ude;$(VSInstall Dir)SmartDevice s\SDK\SmartPhon e2003\include;$ (VCInstallDir)c e\atlmfc\includ e;$(VSInstallDi r)SmartDevices\ SDK\SQL Server\Mobile\v 3.0;;</PropertyValue>
<PropertyValu e
name="IncludeDi rectories">Win3 2|C:\Developmen t\projects\Zipl _src;$(VCInstal lDir)include;$( VCInstallDir)at lmfc\include;$( VCInstallDir)Pl atformSDK\inclu de;$(FrameworkS DKDir)include|x 64|$(VCInstallD ir)include;$(VC InstallDir)atlm fc\include;$(VC InstallDir)Plat formSDK\include ;$(FrameworkSDK Dir)include|Poc ket
PC 2003
(ARMV4)|$(VCIns tallDir)ce\incl ude;$(VSInstall Dir)SmartDevice s\SDK\PocketPC2 003\include;$(V CInstallDir)ce\ atlmfc\include; $(VSInstallDir) SmartDevices\SD K\SQL
Server\Mobile\v 3.0;|Smartphone 2003
(ARMV4)|$(VCIns tallDir)ce\incl ude;$(VSInstall Dir)SmartDevice s\SDK\SmartPhon e2003\include;$ (VCInstallDir)c e\atlmfc\includ e;$(VSInstallDi r)SmartDevices\ SDK\SQL Server\Mobile\v 3.0;</PropertyValue>
<PropertyValu e
name="SourceDir ectories">Win32 |$(VCInstallDir )atlmfc\src\mfc ;$(VCInstallDir )atlmfc\src\mfc m;$(VCInstallDi r)atlmfc\src\at l;$(VCInstallDi r)crt\src|x64|$ (VCInstallDir)a tlmfc\src\mfc;$ (VCInstallDir)a tlmfc\src\mfcm; $(VCInstallDir) atlmfc\src\atl; $(VCInstallDir) crt\src|Pocket
PC 2003
(ARMV4)|$(VCIns tallDir)ce\atlm fc\src\atl\;$(V CInstallDir)ce\ atlmfc\src\mfc\ ;$(VCInstallDir )ce\crt\src\|Sm artphone
2003
(ARMV4)|$(VCIns tallDir)ce\atlm fc\src\atl\;$(V CInstallDir)ce\ atlmfc\src\mfc\ ;$(VCInstallDir )ce\crt\src\</PropertyValue>
<PropertyValu e
name="Executabl eDirectories">W in32|$(VCInstal lDir)bin;$(VCIn stallDir)Platfo rmSDK\bin;$(VSI nstallDir)Commo n7\Tools\bin;$( VSInstallDir)Co mmon7\tools;$(V SInstallDir)Com mon7\ide;$(Prog ramFiles)\HTML
Help
Workshop;$(Fram eworkSDKDir)bin ;$(FrameworkDir )$(FrameworkVer sion);$(VSInsta llDir);$(VSInst allDir)\SDK\v2. 0\bin;$(SystemR oot)\SysWow64;$ (FxCopDir);$(PA TH)|x64|$(VCIns tallDir)bin\x86 _amd64;$(VCInst allDir)bin;$(VC InstallDir)Plat formSDK\bin;$(V SInstallDir)Com mon7\Tools\bin; $(VSInstallDir) Common7\tools;$ (VSInstallDir)C ommon7\ide;$(Pr ogramFiles)\HTM L
Help
Workshop;$(Fram eworkSDKDir)bin ;$(FrameworkSDK Dir)lib\win64;$ (FrameworkDir)$ (FrameworkVersi on);$(FxCopDir) ;$(PATH)|Pocket
PC 2003
(ARMV4)|$(VCIns tallDir)ce\bin\ x86_arm;$(VCIns tallDir)bin;$(V CInstallDir)Pla tformSDK\bin;$( VSInstallDir)Co mmon7\Tools;$(V SInstallDir)Com mon7\IDE;$(VSIn stallDir)Common \Tools;$(VSInst allDir)Common\I DE;$(VSInstallD ir);$(Framework SDKDir)Bin;$(PA TH);|Smartphone
2003
(ARMV4)|$(VCIns tallDir)ce\bin\ x86_arm;$(VCIns tallDir)bin;$(V CInstallDir)Pla tformSDK\bin;$( VSInstallDir)Co mmon7\Tools;$(V SInstallDir)Com mon7\IDE;$(VSIn stallDir)Common \Tools;$(VSInst allDir)Common\I DE;$(VSInstallD ir);$(Framework SDKDir)Bin;$(PA TH);</PropertyValue>
</ToolsOptionsSub Category>

and i did set an env variable VCInstallDir to the correct path(which i am
hoping would override whatever studio has)

C:\Documents and Settings\User>s et VCInstalldir
VCInstallDir=C: \Program Files\Microsoft Visual Studio 8

Am I missing something.

Also want to metion that i do have 2 third party math libraries(*.lib ) that
are not built using VS2005. But they do link fine using VS2003 and VS6.00.
Not sure if this should have any effect.

Regards
Bk
"Carl Daniel [VC++ MVP]" wrote:

"BK-Chicago" <BK*******@disc ussions.microso ft.comwrote in message
news:89******** *************** ***********@mic rosoft.com...

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::PostNcDes troy(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::PostNcDes tory( ) 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|P rojects and Solutions|C++
Directories to make sure that the VS2005 directories are the only ones on
the library search path.

-cd

[BK-Chicago]

The issue has been resolved.

The following actions were taken to resolve the issue:
1. VS 2005 was uninstalled
2. Visual Studio .NET2003 was uninstalled
3. VS 2005 was uninstalled
4. A clean rebuild.

Looks like the initial installation order of
VS 6.0
VS 2005
VS.NET2003
throws the env in a form that confuses VS2005.
"BK-Chicago" wrote:

Thank you for looking into this.

This is what i have set in the Tools Option category.

<ToolsOptionsSu bCategory name="VCDirecto ries"
RegisteredName= "VCDirector ies" PackageName="Vi sual C++ Project System
Package">
<PropertyValu e
name="LibraryDi rectories">Win3 2|$(VCInstallDi r)lib;$(VCInsta llDir)atlmfc\li b;$(VCInstallDi r)atlmfc\lib\i3 86;$(VCInstallD ir)PlatformSDK\ lib;$(Framework SDKDir)lib;$(VS InstallDir);$(V SInstallDir)lib |x64|$(VCInstal lDir)lib\amd64; $(VCInstallDir) atlmfc\lib\amd6 4;$(VCInstallDi r)PlatformSDK\l ib\amd64;$(VSIn stallDir)SDK\v2 .0\lib\amd64|Po cket
PC 2003
(ARMV4)|$(VSIns tallDir)SmartDe vices\SDK\Pocke tPC2003\lib\ARM V4;$(VCInstallD ir)ce\atlmfc\li b\ARMV4;$(VCIns tallDir)ce\lib\ ARMV4;|Smartpho ne
2003
(ARMV4)|$(VSIns tallDir)SmartDe vices\SDK\Smart Phone2003\lib\A RMV4;$(VCInstal lDir)ce\atlmfc\ lib\ARMV4;$(VCI nstallDir)ce\li b\ARMV4;</PropertyValue>
<PropertyValu e
name="Reference Directories">Wi n32|$(Framework Dir)$(Framework Version);$(VCIn stallDir)atlmfc \lib|x64|$(Fram eworkDir)$(Fram eworkVersion);$ (VCInstallDir)a tlmfc\lib\amd64 |Pocket PC 2003 (ARMV4)||Smartp hone 2003 (ARMV4)|</PropertyValue>
<PropertyValu e
name="ExcludeDi rectories">Win3 2|$(VCInstallDi r)include;$(VCI nstallDir)atlmf c\include;$(VCI nstallDir)Platf ormSDK\include; $(FrameworkSDKD ir)include;$(Fr ameworkDir)$(Fr ameworkVersion) ;$(VCInstallDir )atlmfc\lib|x64 |$(VCInstallDir )include;$(VCIn stallDir)atlmfc \include;$(VCIn stallDir)Platfo rmSDK\include;$ (FrameworkSDKDi r)include;$(Fra meworkDir)$(Fra meworkVersion); $(VCInstallDir) atlmfc\lib\amd6 4|Pocket
PC 2003
(ARMV4)|$(VCIns tallDir)ce\incl ude;$(VSInstall Dir)SmartDevice s\SDK\PocketPC2 003\include;$(V CInstallDir)ce\ atlmfc\include; $(VSInstallDir) SmartDevices\SD K\SQL
Server\Mobile\v 3.0;;|Smartphon e 2003
(ARMV4)|$(VCIns tallDir)ce\incl ude;$(VSInstall Dir)SmartDevice s\SDK\SmartPhon e2003\include;$ (VCInstallDir)c e\atlmfc\includ e;$(VSInstallDi r)SmartDevices\ SDK\SQL Server\Mobile\v 3.0;;</PropertyValue>
<PropertyValu e
name="IncludeDi rectories">Win3 2|C:\Developmen t\projects\Zipl _src;$(VCInstal lDir)include;$( VCInstallDir)at lmfc\include;$( VCInstallDir)Pl atformSDK\inclu de;$(FrameworkS DKDir)include|x 64|$(VCInstallD ir)include;$(VC InstallDir)atlm fc\include;$(VC InstallDir)Plat formSDK\include ;$(FrameworkSDK Dir)include|Poc ket
PC 2003
(ARMV4)|$(VCIns tallDir)ce\incl ude;$(VSInstall Dir)SmartDevice s\SDK\PocketPC2 003\include;$(V CInstallDir)ce\ atlmfc\include; $(VSInstallDir) SmartDevices\SD K\SQL
Server\Mobile\v 3.0;|Smartphone 2003
(ARMV4)|$(VCIns tallDir)ce\incl ude;$(VSInstall Dir)SmartDevice s\SDK\SmartPhon e2003\include;$ (VCInstallDir)c e\atlmfc\includ e;$(VSInstallDi r)SmartDevices\ SDK\SQL Server\Mobile\v 3.0;</PropertyValue>
<PropertyValu e
name="SourceDir ectories">Win32 |$(VCInstallDir )atlmfc\src\mfc ;$(VCInstallDir )atlmfc\src\mfc m;$(VCInstallDi r)atlmfc\src\at l;$(VCInstallDi r)crt\src|x64|$ (VCInstallDir)a tlmfc\src\mfc;$ (VCInstallDir)a tlmfc\src\mfcm; $(VCInstallDir) atlmfc\src\atl; $(VCInstallDir) crt\src|Pocket
PC 2003
(ARMV4)|$(VCIns tallDir)ce\atlm fc\src\atl\;$(V CInstallDir)ce\ atlmfc\src\mfc\ ;$(VCInstallDir )ce\crt\src\|Sm artphone
2003
(ARMV4)|$(VCIns tallDir)ce\atlm fc\src\atl\;$(V CInstallDir)ce\ atlmfc\src\mfc\ ;$(VCInstallDir )ce\crt\src\</PropertyValue>
<PropertyValu e
name="Executabl eDirectories">W in32|$(VCInstal lDir)bin;$(VCIn stallDir)Platfo rmSDK\bin;$(VSI nstallDir)Commo n7\Tools\bin;$( VSInstallDir)Co mmon7\tools;$(V SInstallDir)Com mon7\ide;$(Prog ramFiles)\HTML
Help
Workshop;$(Fram eworkSDKDir)bin ;$(FrameworkDir )$(FrameworkVer sion);$(VSInsta llDir);$(VSInst allDir)\SDK\v2. 0\bin;$(SystemR oot)\SysWow64;$ (FxCopDir);$(PA TH)|x64|$(VCIns tallDir)bin\x86 _amd64;$(VCInst allDir)bin;$(VC InstallDir)Plat formSDK\bin;$(V SInstallDir)Com mon7\Tools\bin; $(VSInstallDir) Common7\tools;$ (VSInstallDir)C ommon7\ide;$(Pr ogramFiles)\HTM L
Help
Workshop;$(Fram eworkSDKDir)bin ;$(FrameworkSDK Dir)lib\win64;$ (FrameworkDir)$ (FrameworkVersi on);$(FxCopDir) ;$(PATH)|Pocket
PC 2003
(ARMV4)|$(VCIns tallDir)ce\bin\ x86_arm;$(VCIns tallDir)bin;$(V CInstallDir)Pla tformSDK\bin;$( VSInstallDir)Co mmon7\Tools;$(V SInstallDir)Com mon7\IDE;$(VSIn stallDir)Common \Tools;$(VSInst allDir)Common\I DE;$(VSInstallD ir);$(Framework SDKDir)Bin;$(PA TH);|Smartphone
2003
(ARMV4)|$(VCIns tallDir)ce\bin\ x86_arm;$(VCIns tallDir)bin;$(V CInstallDir)Pla tformSDK\bin;$( VSInstallDir)Co mmon7\Tools;$(V SInstallDir)Com mon7\IDE;$(VSIn stallDir)Common \Tools;$(VSInst allDir)Common\I DE;$(VSInstallD ir);$(Framework SDKDir)Bin;$(PA TH);</PropertyValue>
</ToolsOptionsSub Category>

and i did set an env variable VCInstallDir to the correct path(which i am
hoping would override whatever studio has)

C:\Documents and Settings\User>s et VCInstalldir
VCInstallDir=C: \Program Files\Microsoft Visual Studio 8

Am I missing something.

Also want to metion that i do have 2 third party math libraries(*.lib ) that
are not built using VS2005. But they do link fine using VS2003 and VS6.00.
Not sure if this should have any effect.

Regards
Bk
"Carl Daniel [VC++ MVP]" wrote:

"BK-Chicago" <BK*******@disc ussions.microso ft.comwrote in message
news:89******** *************** ***********@mic rosoft.com...

>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::PostNcDes troy(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::PostNcDes tory( ) 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|P rojects and Solutions|C++
Directories to make sure that the VS2005 directories are the only ones on
the library search path.

-cd

[Carl Daniel [VC++ MVP]]

"BK-Chicago" <BK*******@disc ussions.microso ft.comwrote in message
news:FA******** *************** ***********@mic rosoft.com...

The issue has been resolved.

The following actions were taken to resolve the issue:
1. VS 2005 was uninstalled
2. Visual Studio .NET2003 was uninstalled
3. VS 2005 was uninstalled

I assume you meant reinstalled...

4. A clean rebuild.

Looks like the initial installation order of
VS 6.0
VS 2005
VS.NET2003
throws the env in a form that confuses VS2005.

That's not shocking. It's probably always best to install in order of
release date...

-cd

[BK-Chicago]

Yep!!.. So here are the steps..

1. VS 2005 was uninstalled
2. Visual Studio .NET2003 was uninstalled
3. VS 2005 was re-installed

"Carl Daniel [VC++ MVP]" wrote:

>
"BK-Chicago" <BK*******@disc ussions.microso ft.comwrote in message
news:FA******** *************** ***********@mic rosoft.com...

The issue has been resolved.

The following actions were taken to resolve the issue:
1. VS 2005 was uninstalled
2. Visual Studio .NET2003 was uninstalled
3. VS 2005 was uninstalled

I assume you meant reinstalled...

4. A clean rebuild.

Looks like the initial installation order of
VS 6.0
VS 2005
VS.NET2003
throws the env in a form that confuses VS2005.

That's not shocking. It's probably always best to install in order of
release date...

-cd