Community Server 2.1 SP1 - Warning Free!
As has been noted in several places already, CS 2.1 SP1 came out a few days ago.
After a bit of work going through the diffs and merging in the changes, I'm pleased to say that the CrankyGoblin has now been SP1ed. SP1ified? esspeewunficated?
Patched!
So why has it taken me so long to push it out then? I've been busy with more changes to my code base.
I'm getting very sick of all the warnings that come up when you compile the CS source code. I don't know about when you compile it against the .net 1.1 framework, but I run against .net 2.0 - and there's deprecated warnings all over the place! Sure, it's no big deal really, but... So I've taken the time to replace all the deprecated stuff with .net 2.0 calls instead. It all seems to work, but there's no guarantee. The hardest one was upgrading the emailing system to use the System.Net.Mail namespace instead of the System.Web.Mail one - emailing appears to still work, but there's probably a couple of small glitches there. There is a wrapper class already present that sends the emails using System.Net.Mail, but now I've made it native throughout. Yeah, I know, no there's no back compatibility - so what? It's my source, and I'll break it if I want to! :) (Well, within the terms of the license agreement anyway...)
The most time consuming one was converting everything to use Page.ClientScript.* instead of Page.* for all the clientscript stuff. Easy to do, but there's a LOT!
So now when I do a complete rebuild of the entire codebase, there's 0 errors and 0 warnings. Unless of course I've got some aspx or ascx files open - the html validation fails big time on all those, and I really can't be bothered to figure it out yet (or even see if it's possible to fix those up :)
I also ticked another thing off my list of improvements/cleanup for Gaptcha. I've now got the database end looking nice (the table and procs are named better, reordered columns and parameters, added some error checking, and moved the datalayer code to a more appropriate place.
Whew - it's been a busy week (and that's not including work 8 hours a day - this is just fun).
If you see anything weird going on (other than, well... you know :), please let me know.