Close - But Not Close Enough

I was hoping to release a new version tonight - but I haven't quite got there :( 

I have completed development of v2.5.0.0 (the next release, the previous one being v2.4.1.1) but the packaging isn't quite complete.  ETA for the release isn't certain, I'm hoping it'll be over the next few days.  Let me know if you want a copy 'as-is' anyway and I'll make it available.

As part of the packaging process I run a home-grown tool which (via reflection) extracts out a 'profile' of all the main assembilies, which I can then compare with a previous version.  This tells us exactly what has changed and auto-generates reports like the one provided here: http://www.morphological.geek.nz/Morphfolia/ReleaseNotes.aspx. 

Here's a running list of the changes I've made, and this will be augmented by the actual changes caught by my reflection / profiling tool mentioned above; appologies for the dump straight from MS Excel.

The two colums are: Whats changed, the class or files affected. 

In addition to these changes I've also refactored a lot of const into static readonly values.  Why?  I decided that duplication was better than dependencies; see here if you're not familiar with the difference between const and static readonly (essentially the former is 'hard-coded' into the DLL where-as the latter is computed at runtime), see: http://stackoverflow.com/questions/755685/c-static-readonly-vs-const and/or http://en.csharp-online.net/const,_static_and_readonly.

Finally, I'm experimenting with using attributes to decorate HttpHandlers and their parameters in order to build self-documenting code; this works exactly like what I've done for AppSettings and Event Ids.  The issue is that it's not a complete docment of the Httphandlers, as the URL is defined in the web.config - but it's a start if you've forgotten how to call something (what parameters it excepts and the values they expect).