Mitch's Blog

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.

This tutorial is a followup to my DNN backup tutorial. This document will discuss how you can restore your DNN site from your database .bak file and your DotNetNuke .zip file. This could be to either restore a damaged DNN installation or to move a DNN installation to a new server.

Another very common question that I see regarding DotNetNuke is when and how should I backup my DotNetNuke site. This topic is VERY important and requires a bit of planning, especially if you do not have direct access to your database server to perform your own backups. In the following sections I will first talk about what you must backup and why some of those items are very important. I will then discuss how to perform a DNN backup and SQL Server backup, both for SQL 2000 and 2005. Finally I will discuss options available for third party modules for performing backups for individuals that do not have direct access to their servers.

This posting is an overview document that provides examples of sending SMTP e-mail from .NET 1.1 and .NET 2.0. It covers the differences between each of the .NET versions as well as the methods needed to send SMTP messages using an authenticated SMTP server. Please see the full posting for detailed information

This follow-up post discusses the process to change a user account to a "host" account via SQL. This is a follow-up from my previous blog regarding creating a DNN Host account via SQL.

This posting provides a guide on how to create a new host account within DotNetNuke from your SQL Database. This is very helpful if you ever get locked out of your host account for any reason or for all of the new DotNetNuke users that have been having installation problems with the host and admin accounts. NOTE: This is provided for your use at your own risk!

I have been answering a large number of questions regarding upgrading from DotNetNuke 4.3.5 to 4.4.1 and have created this document to outline the process to complete the upgrade. Please note that I am not responsible for any data loss or corruption that might result from an unsuccessful upgrade of DotNetNuke. Also, even though this tutorial is guided towards users of 4.3.5 this should work for any 4.x version to upgrade to 4.4.1, the upgrade process for 3.x users is NOT the same.

At one time or another I think everyone has been locked out of a system and not been able to get back in. This can be especially troubling if you happen to be locked out of your administrator account. I have seen many people asking how to reset passwords for the host and admin accounts with DotNetNuke so I thought I would write up some simple instructions on how to change a password via the database for any ASP.NET 2.0 website.

One configuration setting that seems to be overlooked frequently with ASP.NET 2.0’s membership provider is the applicationName setting. This setting is very important if you ever want to move your application from one server to another or if you want to share users between multiple ASP.NET applications.