The development of SPS webparts is just like the development of Asp.net Web controls. However, the authorization of SPs and the use of SPS APIs and other. NET functions are involved in the webpart.
Webpart development is in a non-UI state. In normal cases, the effect of webpart UI must beCodeTo render. The functional code of webpart is written in the background code and processed by the server. ActiveX is a client processing technology. It uses scripts to access and control ActiveX methods and attributes. The script is interpreted and executed by the client browser, and does not involve the server part.
However, it is not difficult to use different ActiveX Components in SPS, because the component that can be embedded in SPS is a webpart, simply put, SPS components are developed in the form of webparts. To use ActiveX in webpart, ActiveX is embedded into sps by means of webpart.
The webpart mentioned above is developed without UI, but it can also be developed in some ways so that webpart can be developed with UI without using code in the background, it is implemented by loading a user control that does not inherit the background code. The user control is mainly used to implement the UI part of the webpart, and the main functions are implemented in the background code of the webpart. Similarly, ActiveX must be embedded in SPS through webpart. The background code of this webpart does not need to be processed, and all functions are processed by Activex, add the tag <Object ID = xxx> that references ActiveX to a user control that does not inherit background code... </Object>, and then use webpart to load the UI of the user control without background code in the background, place the <Object> referenced ActiveX component cab package in an available Directory of the current application, or specify the correct path for the cab package in <Object>, in this way, an ActiveX is embedded into the webpart, and ActiveX can be used in SPS. Similarly, Java Applet can be implemented in this way.
Correct the error if any.