First method: Manually register the DLL
This method is used from IIS 3.0 to IIS 4.0 and to other Web servers. It requires you to execute it on the command line, and go to the target containing the DLL.
Record, and enter:
<drive>:\<asp Dir>\regsvr32 Component_name.dll such as C:\temp\regsvr32 AspEmail.dll
It registers specific information about the DLL into the registry in the server. This component can then be used on the server, but this method has a missing
Trap When the component is registered with this method, the component must be set to the appropriate NT anonymous account to execute the DLL. In particular, some components need to read
Take the registry, so the method of registering the component is simply to unregister the DLL without MTS on the server, using:
regsvr32/u aspobject.dllexample c:\temp\regsvr32/u Aneiodbc.dll
Second approach: Using MTS (Microsoft Transaction Server)
MTS is a new feature of IIS 4, but it provides a great deal of improvement. MTS allows you to specify that only privileged users will be able to access the component, greatly improving the site
Security settings on the server. The steps for registering a component on MTS are as follows:
I) Open the IIS Management Console.
II Expand Transaction Server, right-click "pkgs Installed" and select "New Package" III) Click "Create an empty
Package "IV" to the package named V) Specify the administrator account or use "interactive" (if the server is often using the administrator
Landing words)
VI) now use the right mouse button to click the "components" below the one you just created. Select "New then Component" VI selection "Install
New Component "[B]VII) Locate your. dll file and select next to complete.
To delete this object, simply select its icon, and then select Delete.
Note: In particular, note the second method, which is the best way to debug your own writing components, without having to reboot the machine every time.
