I would love the ability to subscribe to an Author, for example, the prolific Marc Clifton. I've looked around the site and didn't find an obvious way to do it so I assume this feature is not present. Receiving an email when the author posts a new article would be adequate but I would much prefer and RSS or Atom feed that I could add to my feed reader. Thanks!

Marc Clifton wrote:

Agreed. ID is for the OK, and fooID is for FK's.

I agree with this. I have found it beneficial for migrating data between databases (for partitioning or archiving) since with a common name for the primary key I can then write generic scripts to perform the migration and only need to worry about dependencies. I'll often go one step farther and also ensure that any descriptive fields are consistently named within the application (in other words either object.Name or object.Title, not both) allowing every row to be presented generically, eg. for a search results page. (Yes, I'm aware that I can just override ToString() in every class, and I do, but having a consistent column name lets the code generator do that for me.)

Sounds like Kelowna, BC is what you are after. Water skiing, snow skiing, mountain biking. Winters are mild and rarely hit -10. Summers are pleasant with July reaching 30 on a regular basis. Population is around 100,000 and we have a international airport. Job market is a little tougher but if you're the best there is then you won't have a hard time finding work. Housing market is comparable with Calgary and some parts of Vancouver. Not much in the way of rentals.

I'm doing .NET 2.0 these days.

If you could buy only one book on building Server Controls in ASP.NET, which book would it be and why? It seems like I spend the most project time debugging controls and tracing what's going on. I'd like to get a definitive guide to developing server controls so that I can master this and get on with the real work! TIA for you input.

You could add a header that contains the number of objects being transmitted and the size of each object in bytes. The tricky bit would be that since the number of objects being transmitted can vary, so too will the size of the header. An alternative would be to add each object being transmitted to a container and then serialize/transmit/deserialize the container and then deserialize each object in the container.