Cisco Cisco Computer Telephony Integration Option 8.5 Guía Del Desarrollador
Appendix C Migrating From CTI OS 6.0
Migrating a COM CIL Application
C-6
CTI OS Developer’s Guide for Cisco ICM/IPCC Enterprise & Hosted Editions Release 7.0(0)
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 6.0 *.vbp project to the new Microsoft Visual Basic .NET.vbproj format,
open the *.vbp 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
(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vbcon/html/vb
oriUpgradingFromVisualBasic60.asp)
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 6.0 *.vbp project to the new Microsoft Visual Basic .NET.vbproj format,
open the *.vbp 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
(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vbcon/html/vb
oriUpgradingFromVisualBasic60.asp)
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.0 Toolkit. Verify that
the following assemblies are listed under the project references:
Cisco.CTIOSCLIENTLib.dll and Cisco.CTIOSARGUMENTSLib.dll.
the COM CIL interop assemblies provided in the CTIOS 7.0 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
migration tool and set the 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 programming language. Be aware that
there are syntactic and semantic differences between Visual Basic 6.0 and .NET
that your application may have to change to accommodate the new model.
complies with the new Visual Basic.NET programming language. Be aware that
there are syntactic and semantic differences between Visual Basic 6.0 and .NET
that your application may have to change to accommodate the new model.
Step 4
Porting Event Handlers to Visual Basic .NET
Visual Basic .NET now adheres to the event model defined by the .NET
Framework that is based on delegates. The delegates model in .NET changes the
arguments of the events received by a client application such that all the event
handlers that your application had implemented for COM CIL events will require
to adhere to the new model.
Framework that is based on delegates. The delegates model in .NET changes the
arguments of the events received by a client application such that all the event
handlers that your application had implemented for COM CIL events will require
to adhere to the new model.
The migration tool does some work at migrating the event handlers but not always
is accurate for this reason the developer is advised to add new event handlers using
the Visual Basic.NET IDE and move the code in the ported handlers to the new
added handlers.
is accurate for this reason the developer is advised to add new event handlers using
the Visual Basic.NET IDE and move the code in the ported handlers to the new
added handlers.