Hello.
I have a VS2002 C++ proj (with 2 custom-made dll dependencies of which I am unsure whether made in VC++6 or later) that I would like to "convert" to VS2003.
However, I am getting more than 400 LNK errors related to ATL::CStringT upon compilation.
Is this a known issue
Can anyone refer me to some solution please
(I think almost all the classes in the DLL file that uses CString are having problems for some reason)
Sample error is shown below:
LNK2019: Unresolved external sysmbol "__declspec(dllimport) public: static class ATL::CStringT<char,class StrTraitMFC_DLL<char,class ATL::ChTraitsCRT<char> > > __cdecl CShisProfil::GetItemStr( struct ITEMINFO const *, int )" (__imp_ GetItemStr@CShisProfil@@SA AV $CStringT@DV $StrTraitMFC_DLL@DV $ChTraitsCRT@D@ATL@@@@@ATL@@PBUITEMINFO@@H@Z) was referred to by function "public: virtual int __thiscall CTask_VdtServerDriver::PreCreateTask(int)" ( PreCreateTask@CTask_VdtServerDriver@@UAEHH@Z)
Your assistance is very much appreciated.

ATL::CStringT LNK2019 error in VS2003 proj
Barry Smith
What if you don't have the source code for the DLL In that case you cannot convert the DLL from VC6 to VS.NET - can you What is the solution in this case
Best regards
Bo Skjoett
skea
This function seams to return a CString. But note that CString is now a complete templated.
So maybe the DLL/library is talking about a different CString class than your compiler supports.
So if the DLL is from VC6 and return a CString you have to port it into VS.NET 2003.