How to manually uninstall and install ntko
Office document controls?
1. When to manually uninstall and install
In general, the client should have automatic controls, so that when the server control version is updated, the client can enjoy the advantages of automatic upgrade. However, if the control cannot be automatically installed due to client configuration problems or interception by other interception tools, you can manually uninstall and install the control as described in this article. For more information, see this document.
2. to manually uninstall the ntko Office document control, follow these steps:1) You are advised to restart the computer before performing the following steps. If you do not restartMake sure to close all browsers and development tools that may use controls, Such as Visual
Studio.net.if the icycler.exe process exists in the task manager, terminate it. This ensures that there are no processes using controls in the system to avoid uninstallation or deletion failures.
2) DeleteC: \ WINDOWS (winnt) \ Downloaded
Program FilesNtko Office document control under the directory (unauthorized demo version ).
3) ChangeOfficecontrol. CabInOfficecontrol. ocxUnbind and copy:C: \ officecontrol. ocx
4) run the following command from the command line:Regsvr32/U c: \ officecontrol. ocx
You can thoroughly uninstall the control.
3. to manually install the ntko Office document control, follow these steps:
1) SetOfficecontrol. CabInOfficecontrol. ocxUnbind and copy:C: \ officecontrol. ocx
2) run the following command from the command line:Regsvr32 c: \ officecontrol. ocx
Reference ntko In the webpage
<Object> of the Office document control indicates the meaning of each part.
The following code references controls in HTML code:
<Object ID = "tanger_ocx" classid = "CLSID: C9BC4DFF-4248-4a3c-8A49-63A7D317F404" codebase = "/path/to/officecontrol. Cab # version ="
Width = "100%" Height = "100%"><Object> the meaning of each part in the tag is as follows: 1)
Id = "tanger_ocx"Identifies the JavaScript programming identifier of the control through document. All (
"Tanger_ocx") To get reference to the control object.
2) CLSID:
C9BC4DFF-4248-4a3c-8A49-63A7D317F404Ntko
The unique identifier of the Office document control. The browser uses this CLSID to determine
ClientWhether the control has been installed.
3) In codebase =
"/Path/to/officecontrol. Cab # version ="In front
/Path/to/officecontrol. CabTo identify the automatically installed files of the control on the server.
Relative to current webpageAnd
# Version =The version number of the control required by the web page.
To enable automatic control installation,The preceding sections must be correct., EspeciallyCLSID, codebase = and # version =.