This project is read-only.

Upgrading to BlogEngine.NET 2.6

File & Folder Changes

There are new files and folders in BlogEngine.NET 2.6, and some files/folders that existed in previous versions of BlogEngine.NET may no longer exist in BlogEngine.NET 2.6.  Several updates have also been made to the web.config file.

Recommended Path to Upgrade

The cleanest way to upgrade to v2.6 is to start from a v2.6 installation, and then copy your existing data and settings into v2.6. The upgrade steps follow.

A couple of the steps are related specifically to those who use a database for storage, and a couple are related specifically to those who use the default XML storage (non-database). You can skip the steps that don't pertain to your method of storage.

1.  Backup

Make a full backup of your existing BlogEngine installation.  This is very important.  If anything goes wrong, you can always restore to your backup.

2.  Install v2.6

Install v2.6 on your computer, in a new folder.

3.  Web.config file (for non-database installations)

As noted above, because of the changes to the web.config files, it is strongly recommended you use the web.config file that is included with v2.6.  If you have any custom settings in your existing web.config files (e.g. appSettings), it will probably be easiest to copy your custom settings into the BlogEngine.NET v2.6 web.config file.  If you have any custom settings, those can be copied into the v2.6 web.config file now.  Otherwise, you can just use the v2.6 web.config file as-is.

4.  Web.config file (for database installations)

If you will be using a Database for data storage, Web.config files you can use are located in the /setup/ folder.  Because of the variety of changes to the web.config files, it is strongly recommended you start from these sample web.config files, and copy your specific connection string into the sample web.config file.  For example, for SQL Server, in the /setup/SQLServer folder is a file named SQLServerWeb.Config.  For MySQL, the file is /setup/MySQL/MySQLWeb.Config, etc.  Copy this file to the blog root, delete the existing Web.config file in the blog root, and then rename this sample config file to Web.config (i.e. rename SQLServerWeb.Config to Web.Config).

At this point, the Web.config file you copied to the blog root and renamed contains a sample DB connection string.  The sample DB connection string will look similar to:

connectionString="Data Source=MySQLServer;User ID=user;Password=password;persist security info=False;initial catalog=BlogEngine;"

Replace this sample connection string with the connection string in your existing Web.config file.

If you have any other specific customizations to your existing Web.config file (e.g. appSettings), add those into this Web.config file.

5.  Database Upgrade Script (for database installations)

If you are using a Database to store your data in, you will need to run the DB upgrade script.  Each of the /setup folders has an upgrade script.  For SQL Server, it is MSSQLUpgradeFrom2.5to2.6.sql.  For MySQL, it is MySQLUpgradeFrom2.5To2.6.sql, etc.  Run this script in your existing DB.  If you are upgrading from a version prior to 2.5, you will need to first run the upgrade script(s) to get your DB up to v2.5.  For example, if you are upgrading from v2.0, you will need to first run the 2.0to2.5 script, and after that, run the 2.5to2.6 script.

6.  App_Data folder (for BOTH database and non-database installations)

In your v2.6 installation is the App_Data folder.

  • If you are upgrading from v2.5, delete all of the files and folders in the App_Data folder except these ones which are new in v2.6:
    1. packages.xml
    2. packagefiles.xml
  • If you are upgrading from a version prior to v2.5, then delete all of the files and folders in App_Data EXCEPT for the following 4 new items which were new items introduced in v2.5 or v2.6 that you do not have in your App_Data folder so you will want to keep these 4 items.
    1. blogs.xml
    2. The blogs directory directly under App_Data.
    3. packages.xml
    4. packagefiles.xml

Once the files/folders have been deleted from the App_Data folder, copy all of your App_Data contents (files/folders) from your existing blog to the App_Data folder.

Note:  This step should still be performed even if you are using a database since even with a database, the App_Data folder is still used for storing certain items such as files, images and some other small miscellaneous files.

7.  Theme folder, Robots.txt & Other Custom Files

If you have a custom theme, copy your custom theme folder into the v2.6 "themes" folder.  Similarly, if you have customized the robots.txt file, or if you have any other custom files/folders, copy those into the v2.6 folder you have been working on.

8.  Deploy to Web Server

Because you will have files on your web server that no longer exist (or have been moved) in v2.6, it is best to delete all of the BlogEngine.NET files and folders on your web server, and then upload the new v2.6 files and folders you prepared in the previous steps.

Please make sure you have a backup of everything you will delete (see step 1).

After you have deleted the BlogEngine.NET files/folder off your web server, upload the v2.6 files and folders you prepared in the previous steps.

9.  Check App_Data folder Write Permissions

If you deleted the App_Data folder in the previous deployment step, you may need to double check that Write permissions are still set on the new App_Data folder you uploaded.  Even if you are using the Database storage option, certain items such as files & images you include in your blog posts are still saved in the App_Data folder.  BlogEngine.NET can only save files in the App_Data folder if Write permissions are enabled for the ASP.NET account.

You can also use update utility to automate upgrade

FAQs & Troubleshooting

Nothing at this time.

Last edited May 27, 2012 at 6:59 AM by BenAmada, version 6


firatesmer Jan 15, 2013 at 6:16 PM 
Update utility doesn't work. Cannot contact with RTUR.NET. So what the hell will I do?

skahle Aug 23, 2012 at 7:30 PM 
I got it working now, at least on my local computer. I upgraded from 1.6 to 2.0 first, and then to v2.6.

My problem is, now I can't run it on the live server. It is running with Able Commerce. I had the old version running and had to modify the the webconfig file for Able Comm. It worked for a couple years. Now, for some reason v2.6 won't run. Anybody have any suggestions?

Thanks in advance,

Scott Kahle

skahle Aug 23, 2012 at 3:40 AM 
I upgraded from v1.6.1

skahle Aug 23, 2012 at 3:34 AM 
I installed v2.6 and I can't bring up the login page. App_Data has had write permissions enabled.