Now that we’ve laid the foundation of DotNetNuke modules, it is time to start looking at the specific modules. While it would be practically impossible to cover every detail and every API feature of a DotNetNuke component, we do want to look closely enough that you know what you are looking at as you are trying to write your code.
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?
Now that we have something running, it’s time to take a look at the various parts of the DotNetNuke framework. But before we do, we need the all-important question, “Why do we care?”
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.