Chapters
There are some really nice code sample and 1-2 pages describing what's going on. Ideal for getting the point across. It's the sort of thing you would only find when looking though mountains of other people source code.

Some of the interesting items are;
Access a Program Element That Has the Same Name As a Keyword

Strong Named Assemblies

Prevent People from Decompiling Your Code

Base64 Encode Binary Data

Create Dates and Times from Strings

Serializable Object to a File

Chapter 4, Threads, Processes, and Synchronization


Review
It would have been very nice if the authors wrote this book using practical examples. Generally, each chapter is broken into sections, which are ultimately, code blocks and paragraphs describing the code.

There is a nice format of each section, namely, it's broken down further into heading of; Problem, Solution, How It Works, The Code. All nice, and shows the authers thought about the book and how to organise the data effectively.

The down side, is that the "Problem" sections tend to be a technical concept, rather than business / practical problem. It would have been really nice if the Problem section detailed, multiple practical problems in a business mannor rather than technical. eg.

ProblemYou need to coordinate the activities of multiple threads (possibly across process boundaries) to ensure the efficient use of shared resources or to ensure several threads are not updating the same shared resource at the same time.

Re-written as

Problem
You have a background windows service that downloads client XML feeds via
FTP, and you want to effectively use the bandwidth available to increase
the throughput.

Granted it would have involved more code etc. but it would have been nice to have practical business problems etc.

References
www.amazon.com/visual-2005-recipes-problem-solution-approach/dp/1590595890