Packaging ActiveX Controls |
Client Administration |
A PROIV application may use ActiveX controls. If the user runs the Windows client then the ActiveX controls need to be installed on the user's machine. If the user runs the Client Administration then the ActiveX controls need to be downloaded to the client machine.
Unpack the files in the PROIVClient.cab (Using winzip/cabarc or another decompression utility).
Modify the PROIVClient.inf file to add your ActiveX control. For details on how inf files are created refer to Microsoft's 'About INF File Architecture' document.
If you ship more than one control then you need to add one entry for each control. Add the entries next to the proivclient.ocx entry.
For example:
[Your Control Name.ocx]
file-win32-x86=thiscab
clsid=[Your Controls ClassID] {486D2165-6DF1-11D2-AC92-00105A1054F5}
FileVersion=[Version of Users OCX File] 505,0,0,0
DestDir=11
RegisterServer=yes
Run cabarc to repackage the components along with your ActiveX controls.
Sample command (without user controls):
cabarc -s 6144 n PROIVClient.cab ProIVClient.ocx [Put your controls here] PROIVClient.inf proivconst.ini proivenk.dll ProivRes.dll prossl.dll mfc42.dll msvcrt.dll msvcrt40.dll locale.ini MFfocus.dll cp_20285.nls
Code signing. If you do not wish to sign the cab then you can skip this step but if you do then warnings will be generated while the user downloads the control. If you want to use PROIV's signature, contact PROIV. If you want to use your own signature, contact a code-signing authority like Verisign (http://www.verisign.com) and purchase your signature.
Using your own keys run signcode to sign the file.
Details on code signing are available here
A signing command code sample:
SignCode -spc PROIVCert.spc -v PROIVPrivateKey.pvk -n "PROIV Client Administration" -i http://www.proiv.com -$ commercial -t http://timestamp.verisign.com/scripts/timstamp.dll PROIVClient.cab
For details on cab files, refer to Microsoft's 'Packaging ActiveX Controls' document |
Topic ID: 100029