Posts Tagged ‘modules’
DotNetNuke 5.x Can’t Move Module On A Page
October 29th, 2009 | 
Author: 
As I mentioned a couple of days ago, the move to DotNetNuke 5 has brought about a few changes. Some of them are design decisions that are just frustrating, like not being able to see that a module is viewable by the administrators only. Others are bugs, like not being able to press the ENTER key while searching for a user, like we discussed a couple of days ago.
Today I’d like to alert you to a design decision that may cause you some trouble.
VB.NET Hide Module Name
Here’s a quick tip for those of you still using modules in your VB.NET applications.
If you create a module and don’t want to see the module name in your intellisense, you can hide it with an attribute. This can be extremely useful when you have a lot of modules that would show up in your intellisense code and they don’t have names that conflict with each other.
DotNetNuke Modules – Creating the PA
By now you have the basics for creating a DotNetNuke module. The only question we have left to address is, how do we package this all up so that we can install it on another server?
The file we are going to create is called the Program Assembly (PA) and is a zip file that contains all the files that are needed for your module on the server and a file with a DNN extension that defines the module so that all the configuration options we put in DotNetNuke to define the module can be placed on the DotNetNuke installation we will install the PA into.
Posted in DotNetNuke - Module Development | 
Tags: development, dnn, dotnetnuke, modules, pa | 
No Comments »
DotNetNuke Modules – Retrieving Settings
On Monday we discussed how to save setting information for our modules. Today we want to pick back up where we left off and deal with retrieving that information, both in the LoadSettings() method and in the view module.
DotNetNuke Modules – Module Settings
Since each instance of a module that we put on a page should be able to have it’s own configuration information, it is necessary to have some place that will allow us to configure it.
For example, you may have a module which could display itself in a number of different ways. You need some way to set this and the settings ASCX file and the associated codebehind file is the place to do this.
