S. Wolfe said
I think of this book as a cookbook without the fat, or a concept book with some meat. The book discusses topics that are often glossed over in introductory books; exactly the types of things that a responsible .NET developer needs to understand to write efficient and stable .NET applications.
Jake Gay said
Microsoft technology has generated some really good books on software programming over the years. This book is definitely one of them. The difference between this book and the others may lie in the fact that it is published by O'Reilly. This book is devoted to the latest Microsoft technology, but it is really a book that explains the basic principles behind all software programming.
You can read this book and substitute any other language, for example Java, to implement the principles elucidated. Of course, the set of software principles is much vaster than in this book, but there are not too many tomes that concisely and clearly explain the fundamental principles that have to show up in any software application.
And it also shows how elegant a job Microsoft has done with DotNet to implement these ubiquitous principles and make their usage incredibly easy. After the pain and torture of their earlier technology (eg. COM), this shines in contrast. Took me back to the joys of programming in plain old Basic and Visual Basic once upon a time. They must have done something right when the open-source advocates jump to implement their own version of DotNet.
S. Devasundaram said
A Classic Book that begins it's journey, where all books end. The true difference between a casual programmer and a disciplined programmer is more prominent in his/her code when they start using advanced features of the framework. A true programmer knows his stuff in and out and knows how to leverage the features of the framework effectively in every line of code. And to get to that level of proficiency it takes reading and practicing the concepts on daily basis. And if at all, there is any book out there, that will help you, then it is this book. A definite YES. 5 Stars.
Armen Jamkotchian said
Without any second thought I will place this book among the best books on the subject ever published. I hope everybody will agree that there are only a few books that worth reading from the beginning to the end without skipping a page. To me this is one of those rare books.
The author manages to reflect on broad architectural concepts and yet be extremely specific. He was able to present the most complicated aspects of component oriented programming and the C# language in a very simple, yet concise manner. Many complex issues that may turn off even experienced programmers are described in a way that not only are very well understood, but could easily be migrated into a working program. The author has found an absolutely perfect balance of presenting general architectural aspects of the subject he is discussing and real life implementation techniques.
I truly believe that anybody who is dealing with such aspects (to name but a few) as serialization, asynchronous invocation, multithreading, reflection, events, delegates, deterministic finalization, etc., MUST read this book.
By the way, this author has published another wonderful book on Windows Communication Foundation - "Programming WCF".
Fabio Santos Franco said
This book is incredibilly well written and has a very comprehensive way of explaining the ways of Component oriented programing. Explains its differences betweent COP and OOP. You can easily understand what the author has in mind, BUT, I found one big flaw on this book. Not that this flaw will make the book less comprehensive, but it will make it less fun.
In all concepts it presents Examples, but not exercises. It explains the features and then give a short example to it. It doesn't stimulate the reader to actually build a code within a major context. You read, see the example and move on to the next topic. It is not fun to just stay around and read and read and read without actually working with the book. It is still a great book, but the approach to the reader could be better.
Comments