Home » DotNetNuke - Module Development » DotNetNuke Modules – Where Stuff Shows Up

DotNetNuke Modules – Where Stuff Shows Up

We continue our series on creating DotNetNuke modules today by showing you where the various components of the module we created last week show up in DotNetNuke.

Remember, last Thursday, we registered the user controls that the DotNetNuke module wizard created for us but I told you not to run them yet because they would throw an error if we did.  So, the first thing we need to do today is to clean up the code so that it will run.  The wizard inserts code that you would use if you were going to create some kind of link manager.  The main problem here is that the code they wrote assumes you already have the data access layer and the controller written.  Since this tutorial is going to work from the top down, at the very least you need to comment out the code between the try and catch statements in the Page_Load method of the ViewDMBSample.ascx(.cs) files.

You can remove the other controls in the edit and settings module too.  You’ll need to remove the references to them in the code-behind if you do.

When you run the code, you’ll notice that the main View module is what shows up when you add the module to a page, the settings module is what shows up in page settings, and the edit module is what displays when you select the “Add” menu option off the module menu.


Other post in DotNetNuke - Module Development

Like this Article? Subscribe to get every article sent to your email.

Related Post

  • DotNetNuke Modules – Creating Base ModulesDotNetNuke Modules – Creating Base Modules Now that we have DotNetNuke installed into Visual Studio we can go ahead and create our first modules. Actually, creating the modules is pretty simple. But it is even easier to do it […]
  • DotNetNuke – Make Your Module SearchableDotNetNuke – Make Your Module Searchable So far, you know everything you need to know to get a basic module up and running. There are a few items we still need to cover regarding the configuration of your module so that it can […]
  • DotNetNuke – Modules – Linking within the moduleDotNetNuke – Modules – Linking within the module Now that we have the module skeleton up and running and we have a data access layer, the next thing we need to look at is specific functions you may need to use from within your code. One […]
  • DotNetNuke – Modules – Portal Specific ModulesDotNetNuke – Modules – Portal Specific Modules Many of you won't care too much about creating Portal Specific Modules because you'll be creating modules for an environment that only has one portal. However, if you are creating a […]
  • DotNetNuke Modules – Making Content PortableDotNetNuke Modules – Making Content Portable The last main feature of module development that we need to discuss is the implementation of IPortable.If you've ever worked with other content management systems in a corporate […]

About Dave Bush

Dave Bush is a Full Stack ASP.NET developer. His commitment to quality through test driven development, vast knowledge of C#, HTML, CSS and JavaScript as well as his ability to mentor younger programmers and his passion for Agile/Scrum as defined by the Agile Manifesto and the Scrum Alliance will certainly be an asset to your organization.

2 Pingbacks/Trackbacks

  • Pingback: Creating DotNetNuke Modules()

  • Pingback: DotNetNuke Modules - Install DNN into VS 2008()

  • http://www.stonefieldquery.com Chris Wolf

    Is there supposed to be a video available with this post?

  • Dave

    There was going to be, but I don’t really see much need and the one I created ended up not being usable.

  • Rick

    I was dying on this one. After completing these steps I could not add my control to a page.

    The problem: I entered a value in the Key field when I defined the main view. A couple hours later I cleared the Key field and *bing* the control appeared!