Customer Reviews

Accelerated C# 2010 (Expert's Voice in C#)

5 star:		(2)
4 star:		(3)
3 star:		(1)
2 star:		(1)
1 star:		(1)

 

 

This book was "Accelerated" to the market to capture market share of developers needing C# 4.0 information before the really good C# books are released. It is obvious that this was based on the old C# 3.0 stuff but some scant 4.0 stuff and a title were given to it in a hurry. The book is poorly written and disorganized and inconsistent. Some important types and topics don't even have an example code of how they are used. The typography is congested and hard to read. If you really want a good C# 4.0 book in a hurry buy the "C# 4.0 in a Nutshell". Otherwise wait for better C# authors to have their updates. This was a total waste of time for me and I'll be returning it.

Though there's some validity to the earlier reviewer's complaint about this book being rushed to market to capitalize on the release of VS 2010, the book is a great reference for the C# language and contains a lot of useful material. It also contains some terrible prose: "A strongly typed language and its compiler form a dynamic duo capable of sniffing out bugs before they strike". Can you picture Batman and Robin sniffing for fanged striking bugs? We know what he meant though, which is the point of a reference like this.

It contains a nice section on threading in C#, and another nice discussion of programming style in C#. So to me it was well worth the price.

This book is a very thorough as far as the C# Language is concerned and is a good reference, but it did feel like several of the C# 2008 books I've already read in the past. If you're looking for a book diving deep into what's new in C# 2010 and .NET 4.0 Framework, then I'm afraid you'll be a little disappointed. If you're familiar with the language then you may find the discussion about the framework evolution, the CLR, and OOP a bit cumbersome. The final chapter finally discusses what's new with the language "Dynamic Types" and it did feel like a high level overview.
Personally, the book felt more like a comprehensive review of the language and would wait for a title more focuses on in C# 2010.

The book is brand new! The interface is good. It
really helped me . I really have some difficulties for my programming class. However, this book gives me some intuition for programming, which makes it easier to do with coding.

Please don't take too serious the comments about the poor quality of this book, they are not true.
Indeed the book is not a complete reference, nor a collection of recipies but is a nice book if your purpose is only to learn C#, let's say is a comprehensive review of the language. A very good job in describing the C# Language.
The examples are also great, so if this is your first C# book, this is the right one.

Well the book did give me some foundations for C# development, it's still kind of a mystery how that happened--but all of a sudden I started using C# and have since made several applications of trivial complexity (for a high level language like C#). C# is also used at my university so over-all, I'm glad I picked up the book or I might not be using C#.

I am still reading the book but so far I have found the author to have done a very good job describing the C# Language.
I am having a very easy time reading thing book due to his great examples and how he describes everything, though some things can get a little wordy but what programming book isn't. I definitely recommend this book for anyone looking to learn C# or further their knowledge in C#.

From my experience with other books by Apres and those found at the Georgia Tech bookstore I began reading the book assuming it could be trusted as authoritative; however, I quickly found inconsistencies, opinion, and outright errors.
For example, on page 46 the author lists the following modifiers as "mutually exclusive... public, protected, internal, and private." I began to question my assumption of the authority of this reference because I seemed to recall that the combination of "protected internal" was valid, it is as is later indicated in the book. Although Nash glibly refers to himself as the "trusty author" (page 279), I found this to be the first of many such inconsistencies.
Nash also imparts his biases about object oriented programming and unsupported opinion such as (page 113) "A huge majority of bugs in native applications come from memory allocation/deallocation mismatches." Firstly, what is a "huge majority" and what support is there for this assertion. In my experience, memory management is, indeed, a source of errors in such code but I don't feel this is sufficient evidence for such sweeping statements and find them to be simply opinion when I look to programming books for hard facts.
I suggest you find a book which is more carefully edited for correctness and more free of opinion.