I am running into a whole lot of errors in trying to update from Rainbow v1.4.0.1763 to 1.4.0.1764

*After the first CVS update, I didn't get the 1.4.0.1764.sql script.  This generated an error (can't find the script file!) when I tried to let the site update itself.  I ran CVS update again and it came down. 

*Once the site updated and loaded, now the signin module doesn't load...I get this message:

"Unable to load control 'DesktopModules/ SignIn/ SignIn.ascx'!"

*Line 215 of SettingsTable.cs (myControl.LabelForControl = editControl.ClientID;) throws the error

"(myPath)\ Rainbow\ Configuration\ Settings\ SettingsTable.cs(215): 'Esperantus.WebControls.Literal' does not contain a definition for 'LabelForControl'"

These errors were related...the first was caused by CVS refusing to download the newest Esperantus.dll (it showed me a conflict during the update) and the second was caused by the reference to the 'old' Esperantus.dll.  To fix it (thanks to a reminder from John Mandia), I:

• Deleted Esperantus.dll from the /bin
• Deleted the Esperantus reference from the project
• Re-ran Update on /bin (so Esperantus.dll was downloaded again)
• Re-added the Esperantus reference. 

* In trying to build the solution, I got a ton of errors like this one:

C:\ (myPath)\ Rainbow\ Configuration\ Settings\ PortalSettings.cs(1300): 'Rainbow.Configuration.ErrorHandler' is defined in multiple places; using definition from 'C:\ (myPath)\ Rainbow\ Configuration\ ErrorHandler.cs'

All of them follow that pattern of 'Class' is defined in multiple places; using definition from 'Class file'.  For most, it looks like I can be rid of the error by deleting the offending class file, then updating it's container folder from CVS (downloading the latest class)...this doesn't make sense to me, though, because I just updated the whole project via CVS.  Anyway, that method doesn't fix all of the errors...I'll have to spend some more time on this later. 

UPDATE Jun 4 2004 - I wiped out the contents of the Rainbow folder, re-updated the whole thing, adjusted the database connection string (as usual), and the darn thing builds just fine!  I guess something about yesterday's CVS update process was beating me....?