A few days ago to do a Web project, you must write an ActiveX control yourself. Most of today's ActiveX controls are developed using vb/c++, and I'm not familiar with them, so consider writing ActiveX controls using familiar C #.
First, create a WinForm control project HelloWorld and drag into a Label control, with the text set to HelloWorld, as shown in figure:
UserControl1.cs contents are as follows:
When you compile the project, you can generate HelloWorld.dll. Copy this DLL to the virtual root directory of IIS and then create a helloworld.htm file with the following HTML code:
In the IE Address bar, enter the following address: http://localhost/helloworld.htm, the interface appears:
As shown in the figure, the control has been successfully displayed on the page. OK, we've finished the first step.
But the problem has not been solved here. Don't believe it? You can try the test on another machine, note that you need to modify the corresponding HTML code and URL address. You can see this is a red fork where the control was originally displayed, or a dialog box appears, indicating that the control does not have any permissions. This result is due to Microsoft's default setting, and the author must execute a security declaration in the assemblyinfo.cs/vb of the control in which the control is located, declaring that the control must use the given permission to display the interface. We refer to the System.Security namespace in AssemblyInfo.cs and add a sentence:
Now recompile, and replace the previous DLL, the interface can be displayed again.
The caveat is that until now, we haven't written a real ActiveX control. So far, this control is only able to implement its own display, and can not achieve more functions, such as the implementation of the script or the operation of the client's registry or disk. This is due to the limitations of the. Net Framework's security model. If we want this control to break through the limitations of the. Net Framework security model, to interact with the script or to manipulate the client's registry or disk, you must make it a real ActiveX control. Below, we turn the control that we just made into a real ActiveX control.
First Use the tool-〉 create a GUID to generate a GUID and modify the UserControl1.cs file. First add the reference System.Runtime.InteropServices namespace and add a statement before the demo:
Note that the string in the GUID is the GUID string you generated. It is the unique identifier of the ActiveX control you are generating. Then modify the project properties, as shown in figure:
Note the last item in the panel, the only thing we need to change is to change its value to true.
Recompile. We use the tool-〉ole/com Object Viewer to view, as shown in figure:
As you can see, the Helloworld.demo we write has been correctly identified as a COM component. Now, we can already display it in a Web page just as you would with other ActiveX controls. In Helloworld.demo click the right mouse button, as shown in figure:
Select Copy HTML <object> Tag to Clipboard, and you can copy the code into the Clipboard.
Now, we rewrite the helloworld.htm,html code as follows:
With IE view, our controls can also be displayed in the Web page. This time, however, it is no longer a previous. NET WinForm control, but a genuine ActiveX control.
However, the task of writing ActiveX controls has not yet been completed. We have not implemented scripting interaction or read/write I/O, nor implemented automatic distribution of ActiveX controls. In the next blog, I'll finish writing ActiveX controls.
Start building with 50+ products and up to 12 months usage for Elastic Compute Service
1 on 1 presale consultation
24/7 Technical Support 6 Free Tickets per Quarter Faster Response
Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.
A comprehensive suite of global cloud computing services to power your business
Payment Methods We Support
