tl;dr

I needed a book that went more in depth on pure C#. I prefer separate books for APIs such as MVC, Web API, Entity Framework, etc.

Long read

To me the point of reading technical books is to dive in depth. Otherwise, I could just watch Pluralsight videos. With this in mind, I have to leave a disappointed review for this book, even more so since I know how hard work technical books are to write (I have a friend who has done it and it took more than a year from conception to release - the way APIs have been moving in the last few years, by that time the stuff in the book is probably outdated!)

I got as far as page 250 before I quit, so I will not comment on coverage. Looking at the table of contents it seems almost all areas of the language are covered. My issue is that other APIs of the .NET ecosystem have also been included. WPF, ASP.NET, ADO and WCF and MVC probably require separate books on their own. WCF can be so confusing, you really will not get away with the one chapter in this book if an enterprise system makes extensive use of it. And, I have WPF books that easily span 1000 pages.

It seems to me that the book is too short to serve as a reference due to the massive scope. Although someone interested in only C# and the BCL will probably be satisfied, there is probably no reason to have them buy short chapters on the rest of the ecosystem. This is the prime reason why in the end I had to return the book, and go with C# in a Nutshell.

As closing comment, I was perplexed to find screenshots from Visual Studio, along with tips and explanations of how to use the editor. I would much prefer if a programming book is IDE-agnostic. The classic Visual Studio has strong competition from Visual Studio Code, which is used widely in Google and even Amazon is considred it.. Not to mention the excellent JetBrains Rider.