I had taken these notes down last week when I updated my Community Server-based blog and forgot to post them. To set the stage, for each blog upgrade I create a new site and new database to fully preserve the previous version for both an archival record and as a reference. I'm now on my third development site: dotText .95 (dbvt), Community Server 1.0 (dbvtcs), and now Community Server 1.1 (dbvtcs11.)
1) Unzipped cs_1[1].1_src.zip
2) Created a new database in development. Restored from CS 1.0 production database
3) Ran CS_1.0_to_1.1_upgrade.sql and cs_procedures.sql on new CS 1.1 database. Received some maximum row size warnings on 'aspnet_Profile' but otherwise upgrade script seemed to run successfully.
4) Created new IIS site for CS 1.1. Copied \web folder contents to root of the site and modified communityserverweb.csproj.webinfo for dbvtcs11 url of development site.
5) Loaded CommunityServerWeb.sln in VS2003, added CommunityServerWeb project from new IIS site, set as startup project
6) Ran exec cs_system_AddNewUrl 'localhost/cs', 'dbvtcs11' to add new CS1.1 site to database
7) Updated web.config. Added SQL connection string to new CS 1.1 database.
8) Ran Ken Robertson's SingleBlog SiteUrls Generator at http://www.qgyen.net/csaddins/singlesite/.
9) Created a /blog directory and added a default.aspx page for single blog URL
10) Added references to CS.Components and CS.Controls projects from CS.Web project to fix "dependencies not found" runtime error
11) Downloaded all gallery images not present on my development server so I could work in CSGalleries area, since CS 1.1 and 1.0 generate runtime error if any photos are not found
Site up and running about 2 hours of working through initial site update and configuration issues.