Sueetie Version 3.0 was released over the weekend, so the first thing I had to do of course was upgrade DBVT.COM from Sueetie v2.0 and .NET 3.5 to Sueetie v3.0 and .NET 4.0. I thought I’d walk through the process to share a few tips and tricks with other Sueetie 2.0 users who are planning a move to v3.0 and .NET 4.0.
As you may already know, Sueetie v2.x upgrades are application-specific, starting with YetAnotherForum.NET, then Gallery Server Pro, ScrewTurn Wiki and BlogEngine.NET. The final 2.x upgrade took the community from .NET 3.5 to .NET 4.0. This may seem like a lot of upgrades, but in reality it’s only two main processes as you’ll see: updating the apps and updating the .NET runtime.
As we being the process our v2.0 site is running .NET 3.5 so we need to knock out the application upgrades in v2.1 through v2.4. On a development server we update our /forum, /media, /wiki and /blog contents with the respective v2.x upgrade package contents. You’ll notice on DBVT.COM there is no forum or wiki, but the Sueetie SQL data schema assumes all applications are installed, so we "upgrade" the forum and wiki whether they’re used on the site or not.
Notice, I said "development server." Let’s also use a development SQL database as well, a mirror of our production database. I had to tweak the script since I use a "photos" application key for the media library, for instance, so you might encounter some environment-specific issues in the upgrade scripts. We’ll be running 4 sets of scripts (5 if you’re using the SQL database provider for BlogEngine.NET rather than the XMLProvider like I am at DBVT.COM.) We’ll touch on those scripts as we continue.
Okay, we’ve updated the contents of our /app folders from the v2.x upgrade packages. Time to walk through the wizards and complete the upgrades. We start with YetAnotherForum.NET by going to http://oursite/forum/install/default.aspx and the YAF Upgrade Wizard. The YAF Upgrade completes v2.1, which also executes Sueetie-specific SQL updates.
Next to Gallery Server Pro. http://oursite/media/upgrade.aspx. Walking through the GSP wizard updates Gallery Server Pro as well as Sueetie-specific SQL updates and completes the v2.2 upgrade.
Now for Sueetie v2.3, the ScrewTurn Wiki application update. After the /wiki contents are updated, the upgrade consists solely of running the v2.2-to-2.3 upgrade script in MSQuery. The completed script should look like the following.
Updating BlogEngine.NET to v22.214.171.124 is Sueetie Version 2.4. If you’re using the SQL Data Provider for BE.NET there’s a 1.6-to-2.0 upgrade script in /blog/setup, otherwise, replacing the /blog contents with the v2.4 contents brings us to the end of our .NET 3.5 journey.
We’ve walked through the process of updating our site to Sueetie v2.4, which you will be able to confirm by the Sueetie Version listed on your Administration Home Page. We’ve done this using our Production-Mirrored database. Everything is working as it should, so we’re going to change our connection strings and walk through the wizards and SQL scripts against our production database.
Time for the move to .NET 4.0! We’re updating from Sueetie v2.4 to v3.0 and .NET 3.5 to .NET 4.0, but the upgrade consists mainly of /bin/DLL updates and web.configs. I added a SQL upgrade script as the last minute, only to put the v2.4 upgrade at bit-for-bit parity with the full Sueetie v3.0 release.
I created a fresh DBVT v4.0 Application Pool in IIS, then assigned it to DBVT.COM and the app folders in IIS Manager, applied the /bin and web.config updates and ran the v2.4-to-3.0 Upgrade script. As for the live site update, I updated the website contents and did a database restore from the production database I updated in development. The total downtime for DBVT.COM was less than 10 minutes.
It’s a good feeling to be running the latest version of Sueetie and, for DBVT.COM, of BlogEngine.NET and Gallery Server Pro. It’s also good to know that I can apply v3.1 updates to DBVT.COM, which I can now get back to working on, so stay tuned.