Cisco Cisco Computer Telephony Integration OS 8.5 Developer's Guide
C-1
CTI OS Developer’s Guide for Cisco ICM/IPCC Enterprise & Hosted Editions Release 7.1(1)
A P P E N D I X
C
Migrating From CTI OS 6.0
Introduction
Cisco CTI OS Toolkit Release 7.1(1) is the official release in which Microsoft
Visual Studio .NET is supported and with which it is possible to build Win32
and.NET applications.
Visual Studio .NET is supported and with which it is possible to build Win32
and.NET applications.
In Cisco CTI OS Toolkit 7.1(1), the C++ CIL static libraries are targeted to be
used ONLY with Microsoft’s C\C++ 7.1(1) compiler or equivalent. Therefore,
these libraries will not work if used with an earlier version of Microsoft Visual
Studio (e.g. Visual Studio 6.0). COM CIL 7.1(1) and the CTI OS ActiveX 7.1(1)
controls are targeted for use in development environments that support OLE
Automation, ActiveX and COM, for example Microsoft Visual Basic 6.0.
used ONLY with Microsoft’s C\C++ 7.1(1) compiler or equivalent. Therefore,
these libraries will not work if used with an earlier version of Microsoft Visual
Studio (e.g. Visual Studio 6.0). COM CIL 7.1(1) and the CTI OS ActiveX 7.1(1)
controls are targeted for use in development environments that support OLE
Automation, ActiveX and COM, for example Microsoft Visual Basic 6.0.
For existing applications built with earlier versions of the Cisco CTI OS Toolkit
it is necessary to upgrade their build projects to include new parameters required
by the new compilers and the new features in the release. The following sections
describe the migration steps and the new parameters required to build the
application.
it is necessary to upgrade their build projects to include new parameters required
by the new compilers and the new features in the release. The following sections
describe the migration steps and the new parameters required to build the
application.
The goal of the migration procedures described below is to guide the developer
on porting his/her current application projects to the equivalent project model
under Visual Studio .NET and not a guide on how to port an unmanagedWin32 or
COM application to native .NET.
on porting his/her current application projects to the equivalent project model
under Visual Studio .NET and not a guide on how to port an unmanagedWin32 or
COM application to native .NET.