Among the DNN sites that I actively manage is the Orlando DotNetNuke® Users Group (ODUG) website.  There are other user groups using our DotNetNuke® instance too though.  We have been having issues with the size of our database for nearly a year now.  Since this site is on a shared instance of SQL Server, we are limited in how large our database can get.  In order to stay below that limit, I have on many occasions cleared out the tables commonly know to cause this problem, such as the EventLog and SiteLog.  However, we were still living life on the edge of going over our limit.  Since this site doesn’t pay very much, I hadn’t looked much further into it until today.  :)

First of all, I needed to find out what objects are taking up the most space on our database.  Luckily, there is a nice little T-SQL script that...

As more than one person has pointed out over the last couple of months (I am looking at you Chris, and Joe), I have had something of a “love affair” with the DotNetNuke® platform for quite some time.  In short, I do indeed love using it and showing others how they can use it to leverage their talents and resources.  In the technical industry, some might call me an amateur “evangelist” for DNN.  I would agree.  Heck, I have been speaking about it for several years now – sometimes even getting paid for it! 

...

First of all, if you’re asking, “What is that,” let me elaborate.  A WSP module is also known as a “Web Site Project” module.  Basically, what this means is that the module does not need to be precompiled into an assembly (DLL) to run.  It pre-compiles as your web site responds to its first web request.  Alternatively, you can also build your DotNetNuke® modules using the WAP, or “Web Application Project” method.  This method will compile your code behind into one or more neat little assemblies, effectively hiding your source code from anyone that has direct access to the file system of your module and/or website.

I am not going to going any great detail of why you’d want to prefer one method over the other – especially since in some cases, these points may not apply.  In short, myself and many others prefer the WAP method of building a module for one or more of the following reasons:

Hide source code Protect the module from direct...

When I first decided to start a DotNetNuke® user group, I had a vague idea of what I wanted to do.  However, Brian Scarbeau beat me to starting the Orlando DotNetNuke® Users Group...

I am in the middle of finalizing the details and preparations for the largest and most exciting Orlando DotNetNuke® Users Group (ODUG) meeting to date.  Part of the reason for the excitement is because it features Nik Kalyani.  That’s only the beginning though.  There is so much more to look forward to.  For instance, we have joined forces with the local .Net user group, ONETUG.  Both groups have a great chemistry,...