If you try to serialize/deserialize a type which uses the generic Dictionary<TKey, TValue> type with the XmlSerializer then you’ll get an InvalidOperationException, for instance:

There are a lot of discussions on the pros and cons of using the ThreadPool and creating your own threads. Having spent a bit of time reading what others have to say, here’s a summary of the things I’ve picked up on.

Occasionally you might want to make the value of a static or instance field local to a thread (i.e. each thread holds an independent copy of the field), what you need in this case, is a thread-local storage.

Stumbled across this question on StackOverflow the other day, definitely one for the interview! The question goes:

How do you convert a string such as “01110100011001010111001101110100” to a…

One of the less known aspect of the DataContractSerializer is its dependency on the order in which fields are serialized and deserialized.

In the last couple of days or so I have spent some time reading Karl Seguin’s excellent and FREE to download ebook — Foundations of Programming which covers many topics from dependency injection to best practices for dealing with exceptions.

By default, arithmetic operations and conversions in C# are executed in an unchecked context. This means that for a signed integer it overflows from int.MaxValue to…