Cisco Cisco Computer Telephony Integration Option 9.0 Developer's Guide
C-3
CTI OS Developer’s Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted
Release 8.0(1)
Appendix C Migrating From CTI OS 7.1(x) or 7.2(x)
Migrating a Visual Basic 6.0 to Use COM CIL
Step 4
Porting Event Handlers to Visual Basic .NET
Migrating a Visual Basic 6.0 to Use COM CIL
As of Release 8.0(1), Visual Basic 6.0 is no longer supported.
Migrate to Visual Basic .NET and use CTI OS ActiveX Controls
For applications that use the CTI OS ActiveX Controls, it was provided a set of Runtime Callable
Wrapper Assemblies (RCWs) that will allow the NET Windows Forms and Visual Basic .NET to interact
with the CTI OS ActiveX controls. The RCW assemblies are installed in the Global Assembly Cash
(GAC) by the Cisco CTI OS 8.0(1) setup program.
Wrapper Assemblies (RCWs) that will allow the NET Windows Forms and Visual Basic .NET to interact
with the CTI OS ActiveX controls. The RCW assemblies are installed in the Global Assembly Cash
(GAC) by the Cisco CTI OS 8.0(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 .NET 2005*.vbproj project to the new Microsoft Visual
Basic .NET 2005.vbproj format, open the *.vbproj project selecting Open\ Project from the File
command menu in Microsoft Visual Studio .NET. 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 .NET 2005*.vbproj project to the new Microsoft Visual
Basic .NET 2005.vbproj format, open the *.vbproj project selecting Open\ Project from the File
command menu in Microsoft Visual Studio .NET. For details refer to Microsoft’s Visual Studio.NET
help on Visual Basic Concepts
Step 2
Verify references to the CTI OS ActiveX Controls RCW Assemblies
After the migration toll finishes the new ported project must include references to the CTI OS ActiveX
controls RCW assemblies provided in the CTI OS 8.0(1) Toolkit. Verify that the assemblies for the
controls used in your application are listed under the project references. For each control in references
there must be two entries for each control one prefixed with AxInterop.ControlName and Interop.
ControlName. The RCW starting with AxIntero.p is responsible for hosting the ActiveX control on the
.NET Windows Form and the RCW prefixed with Interop. Allows the Visual Basic .NET code to use the
properties and methods exported by the control.
controls RCW assemblies provided in the CTI OS 8.0(1) Toolkit. Verify that the assemblies for the
controls used in your application are listed under the project references. For each control in references
there must be two entries for each control one prefixed with AxInterop.ControlName and Interop.
ControlName. The RCW starting with AxIntero.p is responsible for hosting the ActiveX control on the
.NET Windows Form and the RCW prefixed with Interop. Allows the Visual Basic .NET code to use the
properties and methods exported by the control.
Step 3
Apply Ported Code Changes for Visual Basic .NET
Following the migration report applies all the suggested changes such that you code complies with the
new Visual Basic.NET 2005 programming language.
new Visual Basic.NET 2005 programming language.
Step 4
Porting Event Handlers to Visual Basic .NET