Archive for the ‘DotNetNuke - Module Development’ Category

Changing an Existing DNN Module

G07L0069

Got this question this morning from the “Ask A Question” form.

“How do I make a change in an existing DotNetNuke module?  I want to add new fields to the feedback form.”

I’m assuming the question is about making changes to the module without touching the source code.

Read the rest of this entry »

DotNetNuke SecurityException AspnetHostingPermission

tp_vol4_003

Yesterday I was setting up DotNetNuke for a designer on a computer at a corporate location so that he could start working on CSS for some of our custom modules.  He had an earlier version of DNN installed, so you’d think that it would “just work” but there seems to be a new module or something going on that caused the AspnetHostingPermission exception to get thrown so that we couldn’t even run the web site.

Read the rest of this entry »

DotNetNuke – FileUploadControl Danger!

ppl-wom-027 A couple of days ago I was working with a client who was having trouble using the File Upload Control from within a DotNetNuke module.

The problem we were seeing was that although all the code had been written correctly and looked just like every other implementation of the code I had ever used when the server side tested to see if a file had been uploaded, the file was not there… even though we had just uploaded a file.

What The Expletive?

Read the rest of this entry »

DotNetNuke Modules – Automating the PA

tran-wtr-04 Last week we showed how to create a basic Program Assembly (PA).   You’ll remember that a lot of the process was manual.  And if you make a process manual, it is always open to error.

But there is a better way.  By using the Microsoft Web Deployment Project along with the MSBuild Community Task, you can completely automate all but creating the DNN file.

Read the rest of this entry »

DotNetNuke Modules – Creating the PA

IMG_1420 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.

Read the rest of this entry »

DotNetNuke Sponsor

 

Most Valuable Blogger
Sponsor