From: charlybus
Modules in DNN are automatically registered installed. In the installation package of the module, there is a file extension .dnn, this file contains information used in the module installation. Module installation When a module package is downloaded from the Internet (need to be compressed with .zip), the host account is logged in, open the file management in Host, the mouse is moved to the pencil shape, add new files, and click the file upload page after clicking Select Custom Module, find the module package you downloaded in the browse, point to add, select the added file, point the file. At this time, the module will be automatically installed, and there is an installation information (if there is no installation information, the installer does not start, you need to repeat the above operation, I don't know why, this problem often appears), if the installation is successful, there will be the brightness of the installation completion, if Error information will occur if the installation fails. It automatically performs the following work in the installation: Create a folder equivalent to the module compressed file name in DesktopModules. Unzip the module compressed package. Read the .dnn file, copy the file specified in .dnn to the appropriate folder. (Copy the .dll file to the BIN folder, the rest of the specified file is copied into the module folder, ignore the installation of the specified file) Perform the installation of the database script, execute the .sqlDataProvider file in SQL to install the SQL database, will The .accessDataProvider file is executed in Access to install the Access database. Uninstall when installing an error If an error is installed, it is very troublesome when uninstalling, so you should first back up the database before installation. You should do the following steps after installing an error: Delete the related files in the DesktopModules folder. Delete the related .dll file in the bin folder. Restore the database. This step may not be necessary. Some modules do not have DataProvider, or have not written to the database after an error. If you can't judge or reply, it is better. If you can't restore SQL, first stop the IIS and SQL servers, open the SQL server, open the Enterprise Manager restore. If there is a residual text or information is not cleared, and you do not set an ASPNET (Win2000) or NT Authority / Network Service (IIS_WPG group can also be used in the IIS_WPG group), when rewriting a file Will be wrong, the module cannot be installed. The module definition in the normal unloading point Host, point the pencil shape on the module to be deleted, then delete it in the page appearing. For skin bags and container packages. The installation method is basically the same. In the Chinese version I provide, there is a skin and container named phpdupe, you can install it.
