Using both 32-bit and 64-bit Unicode components if your application is a 64-bit application, e.g. C# application with x86 TargetCPU, 32-bit Microsoft Office application or 32-bit C++ application with Unicode character set enabled Installing 32-bit Unicode components only if your application does support Unicode, e.g. Visual Basic 6 application or 32-bit C++ application with Multi-Byte character set enabled. Installing 32-bit ANSI components only if your application does not support Unicode, e.g.
#CODEJOCK XTREME TOOLKIT PRO V17 TORRENT WINDOWS#
It is important to choose the correct configuration that is compatible with your host application as Windows does not allow mixing the bitness of modules in one address space old programming languages do not support Unicode character set. It is assumed that a developer is familiar with ActiveX concepts and best practices related to a programming language of his choice.Įach Codejock ActiveX component comes in 3 configurations:Ĭomponent file names reflect its configuration, e.g.:Ĭ18.0.1.ocx - 32-bit ANSIĬ18.0.1.ocx - 32-bit UnicodeĬ.圆4.v18.0.1.ocx - 64-bit Unicode The way to work with ActiveX components and related language dependent concerns are beyond this article as it is unique to each programming language. The controls can be used from any development environment and with any programming language that supports ActiveX technology.
One component (.OCX) file exposes a set of classes and interfaces necessary for using controls it provides.
OCX files that must be copied and registered on the target computer where they will be used. Codejock ActiveX Controls Unicode v18.2.0Ĭodejock ActiveX components are standalone.