THIS REVIEW IS STILL IN PROGRESS
---------------------------------
I really don't like the dry way of explaining the subject of this book. WCF (or any programming topic) is dull as it is so why make it worse by the approach of listing facts and have no natural flow of the topic which is complicated even for a senior developer like me.
This is just listing of facts about WCF which is great but that's no way to learn something.
There's no guidance from the author on how to execute a certain example. There's no encouragement to build the example yourself. It's like the author is saying: It's there, you wanna try to build it, go ahead, I won't stop you but don't count on following on with this example because next section it might not be there anymore.
There's no clear distinguishing from the author on which parts belong to WCF classes, which are classes that are built by the author, and which are examples to demonstrate something.
Here's a specific example of the author explaining his work instead of the WCF classes. Page 244 explains the DuplexChannelFactory. It lists some members of the class, the author makes a comment about how it's difficult to use this class because the parameter is of type object and is not type safe (which is correct) then he offers his modified class which is type safe and then start to explain how to use this modified class. Well, I don't want to use this modified class. I just don't want to. Even if it's great, wonderful and amazing. I didn't buy the book to read about Programming Juval Lowy's WCF. No, I want to read about .NET's WCF with all stupidity, flaws, and lack of type safety.