Cisco Cisco Computer Telephony Integration Option 8.5 Developer's Guide

Page of 640
 
4-91
CTI OS Developer’s Guide for Cisco ICM/IPCC Enterprise & Hosted Editions Release 7.0(0)
 
Chapter 4      Building Your Application
Deployment of Custom CTI OS Applications
The Dll files need to be copied and registered on the target system. Registration 
is done by using the Windows utility regsvr32.exe providing the dll name (i.e., 
regsvr32 ctiosclient.dll).
ATL71.DLL is a Microsoft Dynamic Link Library implementing the Active 
Template Library used by CTI OS. It will usually be available on most Windows 
client systems in a windows system directory (e.g. \winnt\syste32 on Windows 
2000). Since CTI OS depends on this DLL, it needs to be copied and registered if 
it is not already available at the target system. 
Deploying Applications using C++ CIL
Custom C++ applications link to the static CTI OS libraries. With your custom 
application, you should also distribute ctiostracetext.exe. For the tracing 
component to work, you need to register it on the system where your application 
will run. To register the trace tool run ctiostracetext /RegServer. Besides 
ctiostracetex.exe, there is no need to ship additional components.
Deploying Applications using .NET CIL
Applications built with the .NET CIL class libraries require the following 
assemblies to be distributed together with the custom application. 
Both assmebly libraries are strongly signed such that they can be installed in the 
Global Assembly Cache (GAC) at the application host computer. Or of prefered 
by the developer they can be at the working directory of teh custom client 
application. 
Library
Description
NetCil.dll
.NET CIL Class library, contains the CTIOS 
object classes
NetUtil.dll
.NET Util Class library, contains helper and 
utility classes used in conjuction with .NET CIL