cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
267
Views
0
Helpful
0
Comments
cdnadmin
Community Member
This document was generated from CDN thread

Created by: Christopher Nagel on 06-10-2010 07:11:22 PM
I have imported / "upgraded" the C++ Phone example project from CTIOS 7.2.4, but the linker is choking with messages like:
 
Error    4    error LNK2019: unresolved external symbol "__declspec(dllimport) public: class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >::iterator __thiscall std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >::end(void)" (__imp_?end@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QAE?AViterator@12@XZ) referenced in function "public: virtual bool __thiscall Arg::IsNumeric(class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >)" (?IsNumeric@Arg@@UAE_NV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@Z)    Argumentslibd.lib 
 
VC++ help says to add this to stdafx.h, but no change resulted:
 
template class __declspec(dllimport) CStringT<TCHAR, StrTraitMFC<TCHAR, ChTraitsCRT<TCHAR> > >;
template class __declspec(dllimport) CSimpleStringT<TCHAR>;

 
I have had already to add the "ignore deprecation" preprocessor switch for a slew of POSIX errors. 
 
NOTE: This may just be standard C++ error stuff - I couldn't tell you.  Has anyone else run into these VS2005/2008 problems?
 
Does Cisco have available either VS 2005 or VS 2008 solution/project files for C++ CIL development?  If so, what version of the CIL would I need, or can I get it as an email to my account address?
 
Many thanks,
Chris

Subject: RE: Cannot build C++ using VisualStudio2005 (or 2008)
Replied by: Christopher Nagel on 07-10-2010 05:42:26 PM
I have opened a TAC case (Sev 3 SR 615656025) and will update the group with the results.
 
Chris

Subject: RE: New Message from Christopher Nagel in Computer Telephony Integration Ob
Replied by: David Lender on 12-10-2010 06:00:52 PM
Depends on which CIL.  For the .NET Cil, ideally you want to know which .NET Framework is targeted by the version of the .NET Cil.  Currently Cisco supports .NET Framework 2.0, so you configure Visual Studio to use that Framework. 



For the C++ Cil and COM Cil, you have to use the version supported by your version of the CIL, which  for 7.5  is Visual Studio 2005.

Subject: RE: Cannot build C++ using VisualStudio2005 (or 2008)
Replied by: Christopher Nagel on 12-10-2010 05:50:09 PM
So far I've learned that the 7.2.x releases require VS 2003 to build but the 7.5.x and higher can reportedly be built with the more up-to-date Visual Studios (2005, 2008, 2010).
 
I am searching for the 7.5.9 disks in order to verify.  I have asked a side-question to determine if there will be any cross-compatibility issues between a 7.5.x client with a 7.2.x server.
 
More to follow...
 
Chris

Subject: RE: New Message from Christopher Nagel in Computer Telephony Integration Ob
Replied by: Shannon McCoy on 12-10-2010 06:33:13 PM
Depends on which CIL.  For the .NET Cil, ideally you want to know which .NET Framework is targeted by the version of the .NET Cil.  Currently Cisco supports .NET Framework 2.0, so you configure Visual Studio to use that Framework. 



For the C++ Cil and COM Cil, you have to use the version supported by your version of the CIL, which  for 7.5  is Visual Studio 2005.

 
I use .Net 3.5 SP1 heavly with 7.2.x and 7.5.x with no problems on hundreds of clients. If you compile the .NET samples you need to set the CheckForIllegalCrossThreadCalls to false on the form and technically it might cause problems but  I have not had any complaints yet. That is not a CIL problem anyway but a known multithread issue with WinForms. If you want to you can just change the active thread to the UI thread before you make the call. As for targeting 2.0 you can use 3.5 and probably 4 if you want as you can just set the target .NET in the config file. .NET 4 actually sets this automatically in the app.config for you now. While I understand it is not officially supported in practice it works just fine because the CIL is just packaging TCP/IP packets and messages for the most part and not calling a bunch of COM interop or Win32 calls which is where most people get into trouble with .NET versions.
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Quick Links