10 Reasons to use DotNetNuke for new websites

As a web design consultant specializing in DotNetNuke, I often get asked the question "why use DotNetNuke?".

Why not use Microsoft's SharePoint, or Content Management Server or some other system? Why not build from a new website from scratch? Decision makers in an organization may not be aware of the pros and cons of the various choices - and they will need good information to make a choice.

Surprisingly, there is very few resources on the web with a list of reasons why to use DotNetNuke, so I have prepared the list below.

1. Have an instant website

Simply download and run the installer, and get an instant website with a huge list of features. This website can be used immediately, will look professional and can be put online straight away. This website will allow you to easily add your own content using the large variety of built in modules. There will be no need to know HTML or other coding languages. To do all this when building a website from scratch would take several months effort - why make this effort when DotNetNuke does so much for you?

2. Plug in module based architecture

Each separate piece of content on a DotNetNuke website is a module. This module based approach allows us to easily layout pages by selecting modules and placing them in the desired place on the page. Changed your mind about a modules location? Simply drag and drop it to where a new location. Try doing that with a website where the positions of items on the page are hard coded - it will require a rewrite just to move the items around. Need some functionality that is not provided by the built in modules? It is easy to write your own module in ASP.NET and plug it in with DotNetNuke's module manager. Or buy a module from a third party module developer, there are many useful modules available at very low prices.

3. Plug in skin based layouts

DotNetNuke skins are a clip on cover for your website, just like the one for your cellphone or mp3 player. The obvious benefit of this is a consistent look and feel across an entire website. Skins are easy to operate, just choose the required skin from a list of skins and the whole website is updated to the new look. Try a different skin on a special occasion, like a christmas themed skin or a anniversary themed skin. Skins are easy to create too, and anyone who can create a html layout can create a skin. Skins even allow those who are not so skilled at design to create a good looking website.

4. Built in security and user management

DotNetNuke contains secure and well implemented built in role based security. Use the built in security administration pages to have full control over who can view and edit your web pages. Have a public area and one or more secured areas. This is very useful for creating websites that charge a subscription for premium content. use the role based security to give editing rights to selected users. Security settings apply to all of the website's visitors including search engines - your restricted pages will not be indexed and will not be found on Google. How many websites have had sensitive documents found on a search engine - far too many! By having built in security from day one, this disaster can be avoided.

5. Built in event and error logging

Want to know if everything is running smoothly on your website? Simply check the built in Event Log page to see what has happened. All errors are caught and logged automatically. Find out immediately what is going on, when it went wrong and where it went wrong. This very useful for anyone developing their own DotNetNuke modules. Websites without built in error logging will not know even know if anything is going wrong - ignorance is bliss? Probably not.

6. Resources available

DotNetNuke has a very large developer community behind it. There are a wide variety of resources available, from free DotNetNuke skins, free DotNetNuke modules, low priced third party modules and skins. Use these resources to add value to your website.

7. Use for any type of web application

DotNetNuke was originally created as a Content Management System, but it was soon realised that it could actually be used as the base for any type of web application. A huge variety of different websites have been created with DotNetNuke.

8. Performance and scalability

DotNetNuke is designed for high performance, and includes built in support for web farms. DotNetNuke has been proven on several high visibility websites, like the Australian National Rugby League website www.nrl.com.au or even the DotNetNuke website www.dotnetnuke.com - with 3.7 million hits per month!

9. Large dotnetnuke community

With over four hundred thousand registered users, DotNetNuke is one of the most popular website development frameworks available. This means there is continuous advancement and improvement in DotNetNuke, modules, skins, support and services.

10. BSD license

DotNetNuke's BSD license allows anyone to make a commercial product or service using DotNetNuke. There are no royalties. No strings, no tricks. Just download and go!

Reasons to use DotNetNuke

We have seen that there are a number of very good reasons for using DotNetNuke for your next website project. So why not download it and try it today?

How to copy the content from a localhost install to a live hosted website

How to export the data from your DotNetNuke localhost install to a live hosted website.

DotNetNuke has the option to create a template. This allows you to create a template of your local setup and use it to rebuild the remote site.

Creating a template allows you to export all of the content you have created in your modules (in the localhost install), this will include all of the data from events, FAQ etc - even the skin settings you have applied per page.

What this means is that you don't have to create a backup of your localhost database & upload it, all you have to do is create a template & DNN will take care of the rest.- easy eh?!

If you are exporting the data from a custom module, you need to ensure that the developer has enabled the import / export data function otherwise this method will not work.

Tip: make sure that you have not changed any namings of skins / modules from your localhost install to the actual live install otherwise this will not work.

1) Install the DNN default install first onto your live site
The install procedure: This is (very basically) what you would normally do: (I will cover this in a later tutorial)
a) Upload all of the DNN install files to your hosting provider (You can download from DNN just the install files that are needed, rather than the full source)
b) Create an SQL Database with a username & password
c) Adjust your web config file to the username & password you specified
d) Type in your URL into a web browser
e) Upon opening DNN automatically installs all of the necessary files to your database
f) You now have a working copy of DNN

2) Install the skins, containers and extra modules you require, upload your logo
The Free DotNetNuke Tutorial: Quick Start Guide Video explains how to upload a logo.

3) from your localhost install, Export the template of that portal - Through Host / Portals / Export Template (make sure you tick export content)

4) DNN will tell you where it has saved the template - there will be 2 files that you need to copy (they will have the name that you specified when you exported the template)

5) Upload these 2 files to the same folder within your live install

6) In your live install go to the top admin control panel - on the rhs select Wizard

7) Choose the template you have just uploaded and select REPLACE content

8 + 9) Choose the default Skins and Containers that you originally specified in your localhost install (in the Admin menu / Site Settings)
(If you have selected different skins for each page, DNN will automatically sort this out for you as long as you have previously uploaded all of the skins and containers)

10) Enter your sites details - the Title, description etc.

11) Choose a logo

12) Click on Finish

13) DNN will automatically install your template with the settings you specified

14) Click on Home to view your complete site with the pages & content from your localhost install

DNN will install your own custom modules to the pages you had in your localhost install, but if it doesn't install the data, then you can transfer that across from your localhost database to your live database using Enterprise Manager & all should work fine.

As I stated above, if a custom module does not export / import the data using the Templates this will be because they haven't enabled the import / export function.

- This information I have compiled together from answering questions in the asp.net forum, if you want to see the full discussion, you can see it here:

http://forums.asp.net/ShowPost.aspx?PostID=1042377

Easy DotNetNuke Installation Guide

This guide to dotnetnuke install prerequisites assumes that you have direct access to the computer

This guide is appropriate for any DotNetNuke version from 4.4.1 up to 5.1.0. This includes major versions such as DNN 4.5.3, DNN 4.6.2, DNN 4.7.0, DNN 4.8.4, DNN 4.9.2, DNN 4.9.4, and DNN 5.1.0.

Note: You should not try to install DNN version 5.0.0 - there are too many bugs present in this version.

You must first install these items, in this order:

1. Internet Information Server (iis) .
2. DotNet framework 2.0.
3. SQL Server (express or 2000 or 2005).
4. If you are using SQL server express then you must also install SQL server management console for SQL server express (a seperate download from microsoft.com).
5. The DotNetNuke website files ... unzip the latest versions install package and copy the files to a physical directory somewhere eg c:\dotnetnuke.

(Full instructions on how to install each of these items can be found on google)

Now you need to configure these items:

1. Create the DotNetNuke database ~ create an empty database and a new database user, using SQL server management studio. eg you might name the database dnn_site and the user dnn_user. Give the new user full dbo access to the new database.

This is why we downloaded SQL server management console for sql server express - it is so much easier to use SQL express if you have the graphical management interface!

2. Configure the virtual directory ~ use IIS to create a virtual directory that points to the physical directory created above eg c:\dotnetnuke. For example, we might name this virtual directory dnn_site. Now make sure that the new virtual directory's properties are correct by right clicking the directory in IIS and choosing properties, and now ...

2a. Check that the default document is set to "default.aspx".
2b. Check that "anonymous access" is turned on.
2c. Check that asp.net framework version 2.0 is selected.

These settings will probably already be set correctly, but must be checked.

2a.

2b.

2c.

3. Configure the physical directory ~ give read/write permissions to the physical directory for either the ASPNET user account if you have IIS 5 (Windows XP) or the NETWORK SERVICE user account if you have IIS 6 (Windows 2003). The permission that you must give is "modify". Then give read (but not write) permissions to the IUSR_machinename account.

for iis 5 give modify permission to the ASPNET account:


Or, for iis 6 give modify permission to the NETWORK SERVICE account:


Give read permissions to the IUSR_machinename account:


4. Create a web.config file ~ the install files do not include a web.config file, as a precaution against accidentally overwritting your exiting web.config file if you are doing an upgrade. So you will need to rename the file release.config to web.config.

5. Enter the correct connection strings ~ open web.config in a text editor (eg wordpad) and edit the connection strings:

5a. First in the connection strings section:

Data Source=(your server name);Initial Catalog=(your db name);user id=(your db user);password=(your db password);" providerName="System.Data.SqlClient"/>

5b. Then in the app settings section:

Data Source=(your server name);Initial Catalog=(your db name);user id=(your db user);password=(your db password);"/>

These keys will already be in your web.config, you just need to change them to contain the correct connection string.

The connection string format is the same for SQL 2000, SQL 2005 and SQL 2005 express (and SQL 2008 as well, if you have just started using that).


These keys will already be in your web.config, you just need to change them to contain the correct connection string information as shown above.


6. Now that all the prerequsites have been installed and configured we can start installing dotnetnuke by opening our web browser and browsing to the virtual directory created above, http://localhost/dnn_site.

If while installing, anything goes wrong due to missing any of the settings above, then delete the database and create a new empty database and start the dotnetnuke install again. The reason for this is that a half completed install will result in a half created database, and it is quicker to start again than it is to fix a half installed database.

If everything has been configured properly, the install wizard will start, and we will choose the custom install setting. We will not choose auto or typical, because the custom install allows us to specify the host and admin user names and password ~ since everyone knows that the default usernames and passwords for dotnetnuke is host/dnnhost and admin/dnnadmin, we will make sure to use different usernames ~ any usernames are ok as long as they are not "host" or "admin".

One more time ~ do not use "host" or "admin" as user names, everyone knows this is the default, so it is a security risk.

6a. Install page 1 ~ choose "custom install"



6b. Install page 2 ~ click "test file permissions", this will work since we have already set the permissions.


6c. Install page 3 ~ we do not need to enter any db information, we have already added it to our web.config, click "test database connection", this will work since we have already set up the database.



6d. Install page 4 ~ just click "next".


6e. Install page 5 ~ enter the host user account name and password, remember not to use "host".


6f. Install page 6 ~ just click "next".



6g. Install page 7 ~ enter the admin user account name and password, remember not to use "admin".



6h. Install page 8 ~ just click "next".



6i. Install page 9 ~ just click "next".


6j. Install page 10 ~ dotnetnuke installation completed successfully.


Now that the DotNetNuke website has been installed, the next step is to read our post essential DotNetNuke settings guide and make sure that everything is running securely and efficiently.

DotNetNuke Modules

Learn how to install DNN Modules

DotNetNuke application is no longer compatible with SiteGround hosting services!

By default the Dot Net Nuke application comes with a lot of modules included in its base package. The process for setting up any of them is easy as 1-2-3.

Learn how to install DNN Forum Modules

Here in three steps you will learn how to install the Forum module and how to administrate it.

Once you are logged into your portal with the host or admin username, at the top of the page you will be able to see a menu similar to the one shown at the picture bellow. Please, select the "Add New Module" by clicking on the radio button. From the module drop-down menu select "Forum". Enter a title of your choose which will be displayed as a title of your future forum. Choose a specific location where you want your forum to be shown from the "Pane" drop down menu. Adjust align and apply the new forum settings by clicking on the "Add" button.

After the page is refreshed you will be able to see your Forum in the location you have selected in the previous step. To fine tune your forum settings, simply click on the Settings icon, located at the right-hand side at the bottom of the forum panel, and you will be able to adjust numerous of features of your forum appearance.

Additionally you will be able to administrate it by simply holding your mouse cursor at the top left corner of the Forum panel and make your choice from the drop down menu.

Learn how to install additional DNN Modules

DNN allows you to add a number of ready-made modules such as Blogs, Galleries, Calendars and other handy tools. They will make your website a better place to visit. The installation of these tools is quite easy - you should simply undertake the three steps described above!

Learn how to install a custom module in DotNetNuke

When you download or buy a DotNetNuke plug-in module, it is delivered as a single .zip-compressed archive file. All you have to do is upload the archive file to the DotNetNuke portal, and DNN will install the module for you.

Go to the host menu and select the Module Definitions.

Here you can see the list of the pre-installed modules. At the top left corner (and on the bottom of the page) there is a drop down menu, where you will be able to see "Upload Module" link.

Browse to the folder where your module is located and select the package you want to upload to your Dot Net Nuke portal. Then click on the "Upload New File" link

The screen will now be full of installation messages. If no errors are reported you will see Success at the bottom of the page.

Now the module is installed and you can place it on any page you like, just as you did with the Forum module during the previous module installation.

We told you it was easy ;).

DotNetNuke Themes

DotNetNuke application is no longer compatible with SiteGround hosting services!

To be able to administrate your freshly installed Dot Net Nuke portal you should login into the DNN admin panel as it shown on the picture bellow.

To be able to upload end manipulate the skins of you page point the mouse over the "Admin" and select "Skins" from the drop down menu.

From the left corner of the page you will be able to select to upload your own skin from the Drop down menu.

Select the skin package you wish to upload by the Browse button and confirm the action by clicking on the "Upload new file" hyperlink.

After the Upload process has finished, you will be able to see the custom log information. Scroll down to the bottom of the page and click "Return"

From the "Skins" and "Containers" drop-down menus select your skin package and the web page will be shortly refreshed.

You have the actions to preview, delete or apply your skins. To apply the skin you have chosen, just click on the Apply link under its image and it will become the theme of your Dot Net Nuke portal. The same way you can change the skins of your containers (menus).

Well done! Now you are able to view your new theme by going to your home page.

DotNetNuke Installation

How to install DNN on your website

DotNetNuke application is no longer compatible with SiteGround hosting services!

To be able to setup the Dot Net Nuke application on your ASP hosting account, first you should configure the application's requirements as appropriate. The Dot Net Nuke application requires a MSSQL database and Virtual Web directory to be created trough your Plesk control panel.

Go to the Plesk login page and enter your login credentials. Confirm them by clicking on the Log in button.

Choose the domain name you want to operate over by clicking on it at the bottom of the page as it is shown on the picture bellow.

How to create a MSSQL database

Here first you should create a MSSQL database. To be able to manipulate your databases and database usernames you should click on the Databases icon.

The Dot Net Nuke application requires a new empty database for its installation. Here you will be able to create it by clicking on the Add new database icon.

Choose your Dot Net Nuke database name and select MSSQL as a database type. Please note that the Dot Net Nuke application currently is not compatible with the MySQL database and thus it would not work with it.

Add a username assigned to have privileges to the database you have just created by simply clicking on the Add new database user icon.

Fill the form as appropriate and confirm the action by clicking on the OK.

How to create a Virtual Web directory

Go back to the domain name by clicking on it at the top of the page as it is shown on the picture below where you should now create a new web virtual directory.

This could be easily done by clicking on the Web Directories icon.

You need a new one, so choose the Add the new virtual directory icon.

Choose the virtual name and enter the path to your web root folder.

If you are planning to install the DNN application in a subfolder of your domain name (for example in http://win.lamzo.com/newdnn) please make sure that you have entered the full path to that directory (in this case /httpdocs/newdnn).

The Dot Net Nuke application requires special permissions in order to operate normally so tick the boxes as shown on the picture. Select the script and executables for Execute permissions and apply the changes by pressing the OK button.

Download and Install DNN

You are now ready with the dependencies (MSSQL database, Virtual Directory) for your new Dot Net Nuke portal.

It is time to download the application itself. The Dot Net Nuke project has its own web page which is located at http://www.dotnetnuke.com/. Open this page and please point your browser to the Downloads button.

The Dot net nuke authors require FREE registration process to be passed before you can download the application. Click on the register hyperlink and follow the registration instructions. If you are already registered you could simply skip this step and go to the download section directly.

Fill the required boxes and click register. Once you are done you will receive an auto-generated e-mail message with the account activation code on the e-mail address you will enter in this step so make sure you will provide a valid one.

Get the account activation code by checking your e-mail box and copy it. Click on the login button. Once you have entered your username and password you will be asked you for the Verification code. Enter it as appropriate and click login.

Here you will need to download the Dot Net Nuke SOURCE files (the highlighted one on the picture bellow) by clicking on the Download hyperlink at the right side of your browser.

You will be redirected to the Source Forge download page where you should select the mirror to download the application from and click the download button.

The download process will be started shortly and when it is finished please, save the application archive in a separate folder on your computer.

You should extract the archive you have just downloaded in a separate folder.

Go to the extracted files directory.

Navigate to the "Website" subfolder.

Copy the relase.config file to a file with a name web.config. You can simply rename the relase.config file to web.config but if you mess up something you will have the core relase.config file untouched.

Rename the copy to web.config

In order to be able to make your new Dot Net Nuke application to work properly your should modify the web.config file. This could be easily done by open it with the text editor of your choice such as WordPad and Notepad.

Find the highlighted lines delete them by pressing your DEL button or choose the Cut option from the right-click menu

Cut the commentary closing tag as shown on the picture and paste it at the end of the line as it is shown on the next picture.

Paste the closing tag here or you can simply enter it manually.

Adjust the settings on the following line with the database details you have created via the Plesk control panel (see above) in the initial step.

There is one more connection string you should adjust in the web.confg file.

Find and delete the following lines using the cut/DEL button of your text editor.

Cut this tag and paste it 2 lines above, at the end.

Paste it here.

Modify the database details as appropriate.

The editing of the web.config file is now finished. Please save the changes you have just made by clicking on the File -> Save button.

There is one more file you will need to edit. Once you are done with it you will be ready to upload and install your Dot Net Nuke portal.

You should locate the DotNetNuke.install.config file which is typically located in the Install subfolder. Once you find it please open the file with your favorite text editor.

Find the following line:

http://www.dotnetnuke.com

and replace it with your website address:

http://www.your-new-dot-net-nuke-portal.com

When you are done, please save the changes and proceed to the next step.

Upload the contents of the Website folder to the desired location of your website using your favorite FTP client application.

Once the upload process has finished you should give read, write and execute permissions for the IUSR and IWAM users for all of the DotNetNuke application files and folders. This can be easily done via the File manager of your Plesk control panel. Once you apply them proceed to the next step. If you experience any difficulties to do this by yourself, please do not hesitate to post a ticket and our support team will be more than happy to assist you.

Now it is time to finish your Dot Net Nuke installation by pointing your web browser to the URL where you have just uploaded the files. The installation process will begin automatically and after a short period of time a screen similar to the picture bellow should appear in your web browser.

Click on the link at the bottom of the page and you will be redirected to your new DNN portal.

You are now ready with the Dot Net Nuke portal base installation.

Please bear in mind that the first thing you should do after the installation process is to change the default passwords with a more complex one for the admin and host accounts due to security reasons. The application comes with 2 default accounts installed. The main superuser account username is host. The administration username is admin. Their default log in details are as follows:

Login: host
Password: dnnhost

Login: admin
Password: dnnadmin

The default passwords could be easily changed by logging into your portal with each of these accoutnts and proceeding as shown on the pictures bellow.

Click on the SuperUser account hyperlink at the right side of your portal.

From this page you should modify your personal settings. To change your password click on the Manage Password hyperlink.

Enter your current Dotnetnuke password and confirm the new one by entering it twice.

To change the password for the admin account the steps you should take are the same.

Well done! Now you are ready with your DotNetNuke installation!