Well, I was trying to Serialize them as part of troubleshooting an apparent bug in the generated TableSchema.Table initialization code (reported yesterday) so that I could do a diff on the XML of the 2 different instsnces I was looking at. Since that failed, I had to use the debugger to compare them prpoerty by property. Serializing them directly probably isn't a common occurrence, but if they are going to be decorated as Serializable, then they should be Serializable.
Also, not supporting a parameterless constructor goes against the Framework Design Guidelines and the .NET best practices of allowing ciomponent initialization to be done via Properties (in arbitrary order) rather than by constructors only. Don't get me wrong, I like having extra constructors for convenience, but they shouldn't be the only way to init the object in a reusable API.
Side Note: I have noticed that it appears that many of the SubSonic classes which have multiple constructors don't appear to use constructor chaining. Is this intentional, or simply an oversight?