I was reading some blog posts and I came across this one.  I really appreciate the fact that David Hayden takes the time to do these reviews - I find them very helpful, and I hope someday to follow his good example and review some books myself.

However, I have a fundamental issue with the book that was reviewed.  Well, maybe not so much the book as it is the title of the book:

Beginning C# 2008 Databases?  I didn't know the C# language had databases in it!

I'm sorry but that is just a horrible title.  Something like "ADO.NET using C# 2008" or "ADO.NET 3.5, with Examples in C# 2008" would have have been so much better.

Yes, I know - I'm being a nitpicker - but for good reason.  For example, the book "Enterprise Patterns and MDA" - absolutely an awesome book - horrible title.  I don't really know what to expect to find in that book from the title - but having read an interview of its author, I knew it was worth looking at.

Take away point:  Please, if you are going to write a book, give it a good, meaningful name!

I was thinking through the Code Access Security (CAS) ramifications of my Cloneable<T> class, and stumbled upon a pretty useful article in the MSDN library.  It makes it clear what permissions are needed for various Reflection.Emit scenarios.

I'm sure I have more testing to do in order to find which scenarios cannot use Cloneable<T>, but I'm hoping that list is a short one.