.NET Answers

I have a friend that is working at a local college who called recently because he was having some trouble with his CSS using the Module Settings feature where you can add additional code for the Module’s header and footer.

If you aren’t already aware of this feature, now would be a good time to learn about it.  it can be used to embed javascript into your form, add or change CSS or even provide additional wrapper code for your module.

(more…)

If you're new here, you may want to subscribe to my RSS feed. Thanks for visiting!

This post has been percolating in my brain for several weeks now and I think it’s finally at the point where it’s “done.”  Well, see…

The problem area is this.  At what point and under what conditions would you write the code yourself vs. using a content management system?  And if you were to use a content management system, which one should you use and why?

Along the way I’ll tell you what my current choices are, but more importantly, I’ll tell you what my thought process is.  So even if you decide to use different tools than I do, you can ask the same questions to select the tools you have decided to use.

(more…)

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?

(more…)

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.

(more…)

So far we’ve done all of our development assuming that we are developing our module for internal use.  To be fair, that’s what most of you all will be doing.  There are a lot more of you who will be developing modules for internal use who will be fine with the architecture I’ve already given you, i.e., all of the files in one project.

But what about commercial projects?

(more…)