It's been two weeks since the Community Server 2.1 Service Pack 1 was released. I've been getting some heat from the Usual Suspects to upgrade (no one at Telligent, interestingly enough. You know who you are.) The SP1 was something I knew I had to apply but not something I was actually looking forward to. I've been quite happy with dbvt.com, thank you, and I made a few slight modifications that would require more than the usual amount of attention paid to the upgrade process. I wasn't just updating the site binaries and a few .ASPX/.ASCX files, I was updating my SDK.
Updating a customized SDK to SP1 was pain-free, truly, and for any SP1 laggards who've been reticent to take the plunge, I took notes! Here's my story.
I started the adventure by downloading both the Service Pack 1 Update (Web only) and the latest CS 2.1 SDK because I wanted the source file changes in the SDK AND the SQL script in the SP1 to update my CS 2.1 database to CS 2.1 SP1. The SP1 SDK doesn't contain a SQL script to update from CS 2.1 to CS 2.1 SP1 (no CS_2.1.61010.1_Update.sql.) I didn't see it anyway.
Here in a nutshell is the process to apply the SP1 to a customized CS 2.1 website and SDK.
- Backup source libraries, SQL database and website essentials (not photos\storage, files\storage, etc.)
- Using WinMerge, compare each project with its corresponding project in CS_2.1.60809.935 to record any changes made to the CS 2.1 source. Notice we're comparing against the CS 2.1 release, not the CS 2.1 SP1. (top screenshot below)
- Using the SourceFileChange List in the SP1, copy changed files from CS_2.1.61025.2 into your working SDK. (second screenshot below.) Any modified source files noted in the previous step are individually WinMerged and updated afterward if necessary.
- Run SQL SP1 Update script.
- Have an icy cold Fresca.
The web updates were mostly CP files, only one skin file (Skin-SideBar.ascx), some .JS files, and no .config files at all (other than a /CP/web.config.) The Web update was the area I had trepidations about, but the update spread wasn't nearly as extensive as I thought it might be.
All in all, upgrading a customized site and SDK to the Service Pack 1 was pretty much a snoozer. Good thing I messed with the CS 2.1 source to make it interesting!
