[Dnn module development] quickly create the dnn module installation package

After developing the dnn module, you always write your own dnn file and manually add the required file to the dnn installation package. This kind of work is not only tedious but also easy to make mistakes. Previously, we used the "Create private assembly" function in the module definition of dnn, but some files cannot be packaged. But I have readProgramIt is not clear that the function of creating the module installation package in dnn is not perfect. The project settings of the self-created module do not conform to the dnn standard.
For an independent dnn Module Project, refer to the document "create a separate solution to develop dnn module" to create a dnn module development environment. If you want to generate a complete dnn module installation package, you need to include all the required files in the project. In this way, when creating the dnn module installation package, dnn can read the content in the project file to package some files required by the module. For the database installation script file, you must place the corresponding script file in the corresponding dataproviders folder, for example, the SQL server data installation script file should be in the \ providers \ dataproviders \ sqldataprovider directory where the module project is located, and. sqldataprovider is used as the suffix (for more information about how to quickly create database installation script filesArticleIntroduction, you can find it on my blog ). For Language Pack files, this must be in the "app_localresources" directory of the module directory. Then, you need to configure the module definition and add a new module definition in the module definition of dnn. Configure the properties of each control in the module. After configuring the module definition, you can use the "Create private assembly" function on the module definition interface to create your own module installation package.
It is worth noting that the installation file directly generated by dnn of a higher version cannot be installed in dnn of a lower version, this is mainly because the module definition of dnn in the later version has an additional attribute. Modify it a bit *. dnn file. In Versions later than dnn3.1.0, you have also added an installation package that can contain source code. dnn is becoming more and more powerful!

Note: In Versions later than 3.1.0, The dnn module definition has a folder name attribute, which indicates the Directory Name of the module. This must be correct. Otherwise, the linkbutton of "create private assembly" will not appear.