How to use OCX in Web, specifiying the version, and install it silently on customer machine

The problem was that our enterprise web application make use of an OCX in native image effects. Maintaining the OCX versions on the clients machines was a nightmare because every time there was a new version of the OCX, every client machine has to install it manually (over about 1000 computers for a customer).

The solution is to include additional attribute in the object HTML tag specifying where the package is and the version needed by the web application.

It worked like this : <OBJECT classid=”clsid:XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX” height=”0″ width=”0″ id=Obj CODEBASE=”../../<%=X.X.X.X”>

The CAB file contains the INF file specifying how the OCX shoudl be installed in the system. You can include your installation package (MSI for example) to remove the old version and install the newer version.


References for the INf file, check the Packaging ActiveX Controls article on MSDN.


Categories UncategorizedTags , ,

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this:
search previous next tag category expand menu location phone mail time cart zoom edit close