Developer Installation Options
The Common Control Objects can be installed in two ways:
Manual "Installation". Download the ZIPped CCO
runtime, which comes in both release and debug versions. Installation
consists of extracting files from the ZIP that you need -- typically a
subset
of the OPOS*.ocx files -- plus registering
these COM objects. The batch file
Register.bat in the ZIP will register all of the CCOs. (For the
debug version, the batch file RegisterDbg.bat
registers all of the CCOs plus two files needed for generating the trace
files.) -
Windows Installer Installation.
Run the
InstallShield .msi file, which will prompt you for a few options.
Automated Installation / Uninstallation
Many -- perhaps most -- vendors that need to deploy the CCOs to registers
will choose to package the needed OPOS*.ocx files,
perhaps as an InstallShield merge module that is part of the overall system
and/or application deployment. The CCOs should be marked for
self-registration.
One may choose to use the available MSI file, and apply standard Window
Installer techniques.
Install the complete CCO package without user prompts by running this
command in administrator mode:
msiexec /passive /i OPOS_CCOs_1.xx.xxx.msi
Uninstall the CCO package without user prompts by running this command in
administrator mode:
msiexec /passive /x
OPOS_CCOs_1.14.001.msi
Last updated:
2015-02-08
| 
