Cisco Cisco Computer Telephony Integration Option 8.5 Developer's Guide
C-2
CTI OS Developer’s Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted
Release 7.5(1)
Appendix C Migrating From CTI OS 7.1(x) or 7.2(x)
Migrating a COM CIL Application
Migrating a COM CIL Application
Migrating a C++ Application that uses COM CIL
A C++ application that uses COM CIL is considered an unmanaged C++ application under Visual Studio
.NET.
.NET.
Step 1
Port Build Project
Using your development environment utilities port your current application build project to the new
platform compatible with Microsoft C\C++ 7.5(1) and made all the adjustments required by the vendor.
For example, to port your Microsoft Visual C++ 7.0 *.vcproj project file to the new Microsoft Visual
C++ 8.0 *.vcproj format, open the *.dsp project selecting Open\ Project from the File command menu
in Microsoft Visual Studio .NET 2005. For details refer to Microsoft’s Visual Studio.NET help on Visual
C++ Porting and Upgrading
(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vccore/html/_vc_porting_home.asp)
platform compatible with Microsoft C\C++ 7.5(1) and made all the adjustments required by the vendor.
For example, to port your Microsoft Visual C++ 7.0 *.vcproj project file to the new Microsoft Visual
C++ 8.0 *.vcproj format, open the *.dsp project selecting Open\ Project from the File command menu
in Microsoft Visual Studio .NET 2005. For details refer to Microsoft’s Visual Studio.NET help on Visual
C++ Porting and Upgrading
(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vccore/html/_vc_porting_home.asp)
Step 2
Set New Compilation Parameters
Note
See
.
Migrate to Visual Basic .NET and use .COM CIL
For applications that the require to use COM CIL in a Visual Basic .NET application, it was provided a
set of Primary Interop Assemblies (PIAs) to allow the VB.NET code call interact with COM CIL objects
and events. The interop assemblies for COM CIL are installed in the Global Assembly Cash (GAC) by
the Cisco CTI OS 7.1(1) setup program.
set of Primary Interop Assemblies (PIAs) to allow the VB.NET code call interact with COM CIL objects
and events. The interop assemblies for COM CIL are installed in the Global Assembly Cash (GAC) by
the Cisco CTI OS 7.1(1) setup program.
Step 1
Port Build Project
Using your development environment utilities port your current application build project to the new
platform compatible with Visual Basic .NET and made all the adjustments required by migration tool.
For example, to port the Microsoft Visual Basic .NET2003*.vbproj project to the new Microsoft Visual
Basic .NET.vbproj format, open the *.vbproj project selecting Open\ Project from the File command
menu in Microsoft Visual Studio .NET 2005. For details refer to Microsoft’s Visual Studio.NET help on
Visual Basic Concepts.
platform compatible with Visual Basic .NET and made all the adjustments required by migration tool.
For example, to port the Microsoft Visual Basic .NET2003*.vbproj project to the new Microsoft Visual
Basic .NET.vbproj format, open the *.vbproj project selecting Open\ Project from the File command
menu in Microsoft Visual Studio .NET 2005. For details refer to Microsoft’s Visual Studio.NET help on
Visual Basic Concepts.
Step 2
Verify references to COM CIL Primary Interop Assemblies
After the migration toll finishes the new ported project must include references to the COM CIL interop
assemblies provided in the CTIOS 7.5(1) Toolkit. Verify that the following assemblies are listed under
the project references: Cisco.CTIOSCLIENTLib.dll and Cisco.CTIOSARGUMENTSLib.dll.
assemblies provided in the CTIOS 7.5(1) Toolkit. Verify that the following assemblies are listed under
the project references: Cisco.CTIOSCLIENTLib.dll and Cisco.CTIOSARGUMENTSLib.dll.
If these assemblies are not in your reference list remove those included by the migration tool and set the
two assemblies described before
two assemblies described before
Step 3
Apply Ported Code Changes for Visual Basic .NET
Following the migration report apply all the suggested changes such that you code complies with the
new Visual Basic.NET 2005 programming language. Be aware that there are deprecated classes in .NET
2.0 that your application may have to change to accommodate the new classes.
new Visual Basic.NET 2005 programming language. Be aware that there are deprecated classes in .NET
2.0 that your application may have to change to accommodate the new classes.