[Dnn module development] module File structure and naming method

Note: This article is all about your own understanding of the development module. If there are any errors, please point them out so as not to mislead everyone.

The first step of dnn module development is to find out what files are required for a dnn module, how to name these files, and what role each file plays.

Take the link module as an example:
From the file structure: (Saves some folders or files, such as bin folders)
Dotnetnuke_3.0.13 .......... dnn root directory
Lists topmodules ....................dnn Module Directory
Links ......
App_localresources... Language Pack used by this module
(The name complies with the Language Pack naming rules: the name of the UI control file. ascx. [name of the Language and Culture Region, which is not required for En-US]. resx)
Providers
Dataproviders
Sqldataprovider... sqlserver database access provider, of course, oracledataprovider and so on
Sqldataprovider. VB. Specific Implementation of Data Access
Dataprovider. VB ...... Data Access factory abstract class
Editlinks. ascx ...... edit the content or UI control of the module (named "Edit + Module name)
Links. ascx...
Linkscontroller. VB ...... business logic access object of this module (named by "module name + controller)
Linksinfo. VB ...... the custom business logic object CBO of this module (named by "module name + Info)
Settings. ascx... this module is used to set the UI control. A module has no specific settings.
Module.css...

From the perspective of Project naming, a module generally has two projects:
1. Module UI Layer, business logic layer, and data access Factory
Project name: company name. Module name
Project location: root directory of the module's file
Program Set Name: company name. modules. Module name
Need to reference: dotnetnuke. dll
2. Data Access Implementation Layer (take sqlserver database as an example. If it is Oracle Data, replace sqldataprovider with oracledataprovider)
Project name: company name. Module name. sqldataprovider
Project location: root directory of the module's file \ providers \ dataproviders \ sqldataprovider
Assembly name: company name. modules. Module name. sqldataprovider
Need to reference: dotnetnuke. dll; Assembly of the corresponding module; Microsoft. applicationblocks. Data. dll

From the installation package:
In addition to the assembly files, UI control files, and Language Pack files generated by the module, there are:
Database Installation File: version. sqldataprovider (this is the installation file for sqlserver, for example, 01.00.00.sqldataprovider)
Dnn file: the list of files used by the module and the installation information. It is an XML file named: Module name. dnn
Database unload file: Uninstall. sqldataprovider (this is the unload file for sqlserver)

Available resources for module development:
Module Development Video (in English, but you can see it ):
Http://www.dotnetnuke.com/Default.aspx? Tabid = 810
Describes how to use templates to develop modules.Code):
Http://dnnjungle.vmasanas.net/Development/Templates/tabid/28/Default.aspx
Module Development Guide (official documentation): dnn program directory \ documentation \ public \ dotnetnuke module developers guide.doc
Unfortunately, the above resources are all in English. It would be nice if someone could translate them or write a tutorial!

If you are free to develop the dnn module, you can simply start or modify it based on the existing module. Experience Development in Practice!

More>