Forum

I am seeing a couple of problems with 2.60. If I create a simple MBCS dialog program, the project compiles, links and runs correctly. If I change the project to Unicode I get linker errors:
Test.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: bool __thiscall CExtCmdManager::ProfileSetup(wchar_t const *,struct HWND__ *,class CExtCmdProfile *)" (__imp_?ProfileSetup@CExtCmdManager@@QAE_NPB_WPAUHWND__@@PAVCExtCmdProfile@@@Z) referenced in function "public: void __thiscall CTestApp::SetupUiAdvancedOptions(void)" (?SetupUiAdvancedOptions@CTestApp@@QAEXXZ)
TestDlg.obj : error LNK2001: unresolved external symbol "public: virtual void __thiscall CExtPmBridge::PmBridge_OnSettingChange(class CExtPaintManager *,class CWnd *,unsigned int,wchar_t const *)" (?PmBridge_OnSettingChange@CExtPmBridge@@UAEXPAVCExtPaintManager@@PAVCWnd@@IPB_W@Z)
TestDlg.obj : error LNK2001: unresolved external symbol "public: virtual void __thiscall CExtWS<class CExtADLG<class CExtResDlg>,301>::EnableSaveRestore(wchar_t const *,wchar_t const *,bool)" (?EnableSaveRestore@?$CExtWS@V?$CExtADLG@VCExtResDlg@@@@$0BCN@@@UAEXPB_W0_N@Z)
TestDlg.obj : error LNK2001: unresolved external symbol "public: virtual wchar_t const * __thiscall CExtResizableDialog::OnQuerySkinnedFontParmName(void)const " (?OnQuerySkinnedFontParmName@CExtResizableDialog@@UBEPB_WXZ)
TestDlg.obj : error LNK2001: unresolved external symbol "public: virtual int __thiscall CExtResDlg::Create(wchar_t const *,class CWnd *)" (?Create@CExtResDlg@@UAEHPB_WPAVCWnd@@@Z)
TestDlg.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: virtual void __thiscall CExtWS<class CExtADLG<class CExtResDlg>,301>::EnableSaveRestore(wchar_t const *,wchar_t const *,bool)" (__imp_?EnableSaveRestore@?$CExtWS@V?$CExtADLG@VCExtResDlg@@@@$0BCN@@@UAEXPB_W0_N@Z) referenced in function "protected: virtual int __thiscall CAboutDlg::OnInitDialog(void)" (?OnInitDialog@CAboutDlg@@MAEHXZ)
TestDlg.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: bool __thiscall CExtCmdManager::SerializeState(wchar_t const *,wchar_t const *,wchar_t const *,bool,struct HKEY__ *,bool)" (__imp_?SerializeState@CExtCmdManager@@QAE_NPB_W00_NPAUHKEY__@@1@Z) referenced in function "protected: virtual int __thiscall CTestDlg::OnInitDialog(void)" (?OnInitDialog@CTestDlg@@MAEHXZ)
TestDlg.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: bool __thiscall CExtCmdManager::CmdSetup(wchar_t const *,class CExtCmdItem const &,bool,bool *)" (__imp_?CmdSetup@CExtCmdManager@@QAE_NPB_WABVCExtCmdItem@@_NPA_N@Z) referenced in function "protected: virtual int __thiscall CTestDlg::OnInitDialog(void)" (?OnInitDialog@CTestDlg@@MAEHXZ)
TestDlg.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: bool __thiscall CExtCmdManager::ProfileWndAdd(wchar_t const *,struct HWND__ *)" (__imp_?ProfileWndAdd@CExtCmdManager@@QAE_NPB_WPAUHWND__@@@Z) referenced in function "protected: virtual int __thiscall CTestDlg::OnInitDialog(void)" (?OnInitDialog@CTestDlg@@MAEHXZ)

That is Visual Studio 2003. If I change back top v2.54 I do not get these errors. A VS2005 project yields similar results. Oddly enough, the 2005 reports fewer linker errors.

The second thing that I see is; I built the libraries using VS2005, using the workspace. No errors reported during compiling. I built the unicode version of the Prof_UIS controls project. When I run the exe, I can see a brief flash as the dialogs start to show and then I get a debug assertion. The assertion is occuring in CEXTLabel::OnDraw() when doing a ReleaseBuffer on a string. I can get the exact line number if you need that.

I have not seen these problems previous to 2.60, so I would imagine that I am doing something stupid. Any ideas on what I am doing wrong?
Thanks

I just finished recompile my project with the 2.60. No problem occurs.

Are you sur you are using all files from the new version ? No older files can be found by the compiler on your system ?

Have you recompile entirely your project ?

Some suggestions I this help you...

Yeah... thanks. The only thing that I haven’t tried is totally removing and then re-installing, which I was hoping to avoid. Guess that is what I am going to have to do.

Personally I don’t use the Prof-UIS installer.

I unzip the file and do a manual installation. So I control my include, lib and other folders.

Some times Visual Studio doesn’t detect changes on some files and links older files with newer...

Well it’s working now. I had to do a uninstall and a reinstall. Like you, I usually do a manual install but this time it didn’t work.

Thanks