Dnn reading excerpt 5-Starter Kit Template

Professional dotnetnuke module programming page4

This excerpt is about the starterkit template in dotnetnuke. We will introduce the following modules after installing startkit. The books are in English and we will translate them here, and some of my understandings.

Dotnetnuke web application framework:This template is the entire dotnetnuke solution that can be used to set up a website for development. This template shocould not be used because development can more easily be completed via manual installations using the install package.

Dotnetnuke web application framework:This template is the dotnetnuke solution, which is used to build a website for development. This template should not be used because we can set up a development site by manually installing dotnetnuke, instead of using the template. The role of this template is equivalent to a dnn installation. We usually use startkit for module development after dnn is installed.

Dotnetnuke compiled module (VB ):This template will create a web application project (WAP)-compiled Visual Basic (VB) module. this template creates all standard dotnetnuke module elements, including the data access layer (DAL) and multiple view controls. this is the template that is used in this book for all VB examples. it creates a module that will be compiled into a single. DLL for distribution via standard build processes.

Dotnetnuke compiled module (VB ):This template creates a web applicationProgramProject (WAP for short)-a compiled module written in VB. This template creates all the standard dotnetnuke module elements, including the data access layer and multiple view controls. All VB examples in this book use this template. The modules it creates are compiled in a separate. dll file and released through the standard generation (compilation + connection) process.

Dotnetnuke dynamic module (VB ):This template will create a web site project (WSP) VB module that utilizes the app_code folder for all classes. this template creates a complete module with similar contents to the compiled module template, including full Dal classes. this template is recommended for users with Visual Studio Express, which prior to Visual Studio 2008 Service Pack 1 cannot support the WAP development model. chapter 2 provides full information on Visual Studio versions and project types.

Dotnetnuke dynamic module (VB ):This module will create a module written in VB language for web project (WSP) and dynamically compile it for all classes using the app_code folder. This template creates a complete module, which has similar content to the compiled module template, for example, they all have a complete data access layer. This module is recommended to those who use Visual Studio express for development, especially those who use Visual Studio 2008 Service Pack 1 because it does not support the WAP development module. Chapter 2 provides detailed information about the Visual Studio version and project type.

This template is implemented as an item template, and may only be added to a dotnetnuke web application framework solution created via the template discussed previusly.

This template is implemented in the form of a project template and may only be loaded to the dotnetnuke web application framework solution. This solution is created using the template discussed earlier.

Dotnetnuke dynamic module (C #):This template will create a web site project (WSP) C # module that utilizes the app_code folder for all classes. the created Project will be exactly like that of the dynamic VB module, but translated to the C # language. this project template is recommended for developers who prefer C # and are using Visual Studio Express.

Dotnetnuke dynamic module (C #):This module creates a module written in C # language for a web project (WSP) and dynamically compiles all the classes using the app_code folder. The project created is very similar to the dynamic VB module, but the VB language is converted to the C # language. This project template is recommended to developers who prefer C # and those who use Visual Studio Express.

This template is implemented as an item template and may only be added to a dotnetnuke Web Application Framework solution created via the template discussed previusly.

Dotnetnuke simple dynamic module (VB ):This template will create a dynamic VB. net module, but the module created will only have a single view control and. dnn manifest. this is designed for individuals looking for a custom implementation, or those looking for a clean project to start.

Dotnetnuke simple dynamic module (VB ):This template will create a dynamic VB. NET module, but the created module only contains a list of attempted spaces and. dnn files. This is designed for people looking for custom implementations or a simple project.

This template is implemented as an item template and may only be added to a dotnetnuke web application framework solution created via the template discussed previusly.

Dotnetnuke skin:The final template has ded In the starter kit creates all files needed to create a single skin and container for a dotnetnuke website. Chapter 3 discusses skins and containers in more detail.

Dotnetnuke skin:The last template in starter kit creates all the files and containers for the dotnetnuke site that need to be used to create a single skin. The third part will discuss skin and container details.