Chapter 16: Skinning DotNetNuke

Summary

This chapter finishes the series on module development and architecture. In Chapter 13, you developed your physical provider class, which provides methods to expose your stored procedures in the database. From there, you moved on to creating an abstraction class, and finally exposing the result set of records as a collection of objects from your Business Logic Layer (see Chapter 14).

In this chapter, you did the following:

• You combined your work with those classes from the previous two chapters and then bound them to your module controls. Modules consist of several types of controls. The more common ones are as follows:

  • The View control, for the first initial view of a module

  • The Settings control, for configuring properties of a module instance

  • The Edit control, for editing information specific to your business logic for the module application

• You learned the various helper functions that you can use in your own projects to reduce the amount of custom code.

This should provide you with enough information to begin developing your own module for DotNetNuke. In Chapter 17, you learn how to package these modules for distribution in other DotNetNuke portals. But first, in Chapter 16, you explore skinning the DotNetNuke application and provide your own unique look for your installation.