The question has appeared multiple times recently regarding methods to convert a standard ASP.NET application into a DotNetNuke module as well as options to “integrate” an existing ASP.NET website into DotNetNuke. This concept is very complicated for many individuals to follow and below I will discuss the options available to those looking to either integrate solutions or to create new DotNetNuke modules from existing applications.

I have received numerous e-mails today regarding an exploit that was used on my site today to direct my forum's page to http://www.google.com.  I have identified the root cause of the issue and am working to resolve the underlying issue.

At this time I have removed the forums module from the general public view.  I will plan on re-enabling this later this evening once I have access to correct the bad database entries.  I have been in contact with the DotNetNuke core team regarding this issue and I have been assured that in 4.5 it should be resolved.

I am also preparing a "Securing the Forums Module" blog which will walk you through a procecdure that I have tested that should prevent this type of exploit from occuring again in the future.

Again, I greatly appreciate the feedback and the prompt notice everyone has given me.  I will work to get this back online as soon as possible!

As you all have noticed from my post above today I identified an issue with a javascript exploit on the forums module. This blog will give you step-by-step instructions on a few simple additions to the word filter that should prevent you from being affected by the exploit.

• Packaging DNN Modules (Included modified core modules) for installation on another DNN Portal
• Upgrading DNN from 3.x -> 4.x with detailed instructions, including disaster planning tips
• Using the DNN Label control
• Installing DNN on Windows Vista and IIS 7
• Creating a DNN Page Template
• SQL Server Performance tuning
  

• CurrentWeatherConditions Module (Free Module, slated for release by 4/1
• Quiz Module - New module planned (Details coming before month end)

Like many ASP.NET programmers I utilize a third party hosting company to host all of my sites. We have all ran into situations where we have been loosing sessions and other oddities and it would be very helpful to find out exactly what caused the application to restart. Well thanks to this post on DotNetNuke.com by Frankt I have found a way to track this information. In this entry I will provide you with code that can obtain this information

So you have created the nice new skin that you have been looking to use with your DNN site, but you don't know how to set it up to upload to your site. Well the process is actually very simple if you follow the steps inside this entry.

I have been asked recently for an example of how to setup the DNN Guestbook 1.0 module to display records in a more traditional guestbook manner. I have just posted a template to the forum that will accomplish this desired look and feel.

If you have a template that you think would be helpful please feel free to share it in the forums!

There have been numerous reports on DotNetNuke.com about errors encountered after switching to a skin with a vertical menu in DotNetNuke 4.4.1 if using a clean installation.  These errors are typically "Null reference exception" errors, however some individuals have received general "an error has occured" messages with a portion of the site still visible.

If you have recently switched to a vertical menu and are receiving these error messages it is quite possible that you are missing a few required .dll files for the vertical menu system.  It appears they were left out of the DNN installation files for 4.4.1.  To fix this issue you will want to download a copy of DotNetNuke 4.3.7.  Once you have downloaded 4.3.7 you will want to copy the following files from 4.3.7's bin folder and place them in your 4.4.1 bin folder.

- DotNetNuke.DNNTreeNavigationProvider.dll
- DotNetNuke.ASP2MenuNavigationProvider.dll
- DotNetNuke.Caching.BroadcastPollingCachingProvider.dll
- DotNetNuke.Caching.BroadcastPollingCachingProvider.SQLDataProvider.dll
- DotNetNuke.DNNDropDownNavigationProvider.dll
- DotNetNuke.DNNMenuNavigationProvider.dll

After you have copied each of these DLL files over you should notice that your errors will go away. 

Good luck!  As always, feel free to provide comments below or ask questions in the forums!