Configure ActiveX controls to download the installation in a Web page

First check that the client browser has ActiveX controls installed, and if you do not have ActiveX installed, you will need to first download the browser and allow the installation. Otherwise, use the ActiveX control directly. We can use CODEBASE to meet our requirements: Here is an HTML call:

<object classid= "clsid:636b8ce1-7512-464c-b63c-fc75bdca21db" codebase= "Charles2008activex /setup.exe#version=1,0,0,0 " Width=" " height=" > </Object >

Note the CodeBase property inside, specifying the path to the installation file: Charles2008activex/setup.exe, version 1.0.0.0. This is a relative path, and the actual decision path is the Setup.exe file in the Charles2008activex folder in the directory where the current URL address is located, which is the installation file for that ActiveX file.

This allows us to use the CODEBASE property to satisfy our requirements for ActiveX controls.

So we need to illustrate another question: How do you package an. exe file or. cab file for an ActiveX control?

is actually creating an installer for the developed ActiveX control. Let's say it's an ActiveX control developed by C #. The packaging process is actually the same as the normal WinForm program packaging process. Note that you need to set up: URL address of the installation: (e.g.)

This is set to Http://192.168.1.101/ActiveX, this directory must exist, to store the generated installation files for the client to download and install.

When the configuration is complete, the build project generates two files, an. exe and an. msi file. Copy the generated EXE and MSI files to the website ActiveX directory.

Start the Web site and make sure that the directory that accesses Setup.exe is the same as the installation URL in [Setup Project]. In general: Web pages will pop up prompting, whether to install ActiveX controls, etc., if prompted or not, you need to add the Web site to the trusted site and allow you to download unsafe and unsigned controls. Installation in this way will eject the installation software interface on the client. Similar to WinForm installation.

We can also package the program to generate a CAB file, which is generated above. MSI files are packaged to generate CAB files, and there are many paving aids such as: CabARC.exe. Usage can refer to other network resources. It is said to be convenient and simple to use. This is not a detailed introduction!

Anyway, we can get the ActiveX package to build the installer we want, and codebase to specify the URL to download the ActiveX control to meet the requirements:

The client has installed an ActiveX control that is no longer installed, and the ActiveX control is not installed and is downloaded and installed from the codebase path, which also satisfies the client's requirements for the control. [Excerpt from http://www.cnblogs.com/Charles2008/archive/2010/04/11/1709844.html]

Configure ActiveX controls to download the installation in a Web page