Holy crap! It worked!!! My mabster360 skin still appears to work and everything!

So - for the benefit of others: I had two errors in my upgrade process, both in the SQL script that brings the membership tables up to ASP.NET 2.0's standards (cs_ASPNET2_Membership_Schema_Update.sql). They were collation errors, and looked like this:

Msg 446, Level 16, State 9, Procedure aspnet_UsersInRoles_AddUsersToRoles, Line 45
Cannot resolve collation conflict for equal to operation.
Msg 446, Level 16, State 9, Procedure aspnet_UsersInRoles_RemoveUsersFromRoles, Line 50
Cannot resolve collation conflict for equal to operation.

Obviously my host's database is running a slightly different collation than the one that the script is running under. The fix was to find this line in both stored procs:

DECLARE @tbNames table(Name nvarchar(256) NOT NULL PRIMARY KEY)

... and add an explicit collation statement, thusly:

DECLARE @tbNames table(Name nvarchar(256) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL PRIMARY KEY)

Re-run the "alter procedure" code for those stored procs, and all was good!

So now ... to investigate all the new features in CS 2.1! First stop ... tags and tag clouds!