Upgrading Custom SSIS Components from SQL 2005 to SQL 2008

We'd had a SQL 2005 box all dressed up for my DW/BI work - but since it's gone a little slower than I'd would have liked[1], SQL 2008 happened to have shipped before any serious test work got underway. That gave me the opportunity to upgrade, and after seeing some of the features in videos from LearnMicrosoftBI (a great starter site) that somehow miss being part of the official release fanfare, I thought that now was a much better time to upgrade than after the work was done.

The first thing I did was, of course, strip SQL 2005 off my dev system and install 2008. Then I searched BoL for an on-topic article, and found this: Upgrading Custom Objects for SQL Server 2008 Integration Services.

Since I was early in the lifecycle of my components, and not "live", I chose the easy upgrade path - no reversioning. You'll have to make sure that you have the SQL Server 2008 "Client Tools SDK" installed on your dev machine. The short version:

1. Replace all of your "SQLServer" References with the version 10 copies.
2. Rename all "xxx90" types as "xxx100" types
3. Fix the errors.
   Changes I had to make were changing the DtsConvert.ToXXX functions to either "DtsConvert.GetWrapper" or "DtsConvert.GetExtendedInterface"
4. Change the directory you deploy to from "...\90\Dts\..." to "...\100\Dts\..."

The only issues I had were:

1. I had a reference to "Microsoft.SQLServer.DtsMsg" which I couldn't find in the 2008 reference list - turns out I didn't need it. Either I wasn't using it, or the code that was in it was moved into one of the more mainstream references.
2. Changing the path I had to GacUtil in my post-build event command line (because I uninstalled VS2005 as well in the upgrade)

Pretty painless. Good work, SQL Server team...
[1] - Just like any "project", the gremlins derail it from time to time - other work crops up, source system changes were required, etc...