Alan Hogan said
The worst-written and most repetitive technical book I've read. Reads like the first rough draft: did anyone edit this book?
This book mentions twice in four pages how amazing it is that C# lets you use "goto" to get around its strict "switch" statements. Both times, the concept is introduced as if to a newbie, and both times, the authors praise Microsoft's infinite wisdom in allowing this. Twice in four pages! Other things repeated over and over at the beginning of the book include the concept that C# is managed code, how .NET saves the world, that C# is like Java, and that C# is not like Java.
Also, consider the following example method:
// This function takes an int array (a reference type)
// and an int (a value type).
static void SomeFunction (int[] Ints, int i)
{
Ints[0] = 100;
i = 100;
}
Amazing, huh? The cleverly named "SomeFunction" takes two arguments and inexplicably sets one and part of the other equal to 100. I imagine they left figuring out _why_ "as an exercise for the reader."
I'm not trying to whine. Some technical books -- The PickAxe, an introduction to Ruby, comes to mind -- have meaningful examples and concise, clear text and are a pleasure to read. _Professional C#_ is just the opposite.
For a book that supposedly requires previous programming knowledge, it sure drags you through the basics of computer science over and over. (That said, do NOT start programming for the first time with this book as your guide. Quite a few times, I remember thinking, "Wow, I'm glad I'm already familiar with the concept of ______ because this is a horrible explanation!")
Someone said this book was long, and that meant it was complete. No, that just means it's wordy and repetitive. You've been warned.
Buonanno Sergio said
It's one of the best C# and .NET Framework introductions, but the problem is that, due to the extent of the subject, all the books that try to cover the whole .NET Framework in a single (even if big) volume are missing the point from a professional programmer point of view.
To have all you need to fully understand the .NET Framework it's absolutely essential to have a collection of books that cover every single topic in detail and they are appearing now.
If you want to save money and buy a good introduction especially about C# or you are an experienced programmer that ventures out to .NET and C# for the first time then it could be a good purchase, otherwise it's better to focus on the topics you are looking for and buy more specialized publications. A professional programmer could find it a little superficial in some parts and due to the usual hurry of Wrox Press to be first on target a little disjointed in others.
Buonanno Sergio said
It's one of the best C# and .NET Framework introductions, but the problem is that, due to the extent of the subject, all the books that try to cover the whole .NET Framework in a single (even if big) volume are missing the point from a professional programmer point of view.
To have all you need to fully understand the .NET Framework it's absolutely essential to have a collection of books that cover every single topic in detail and they are appearing now.
If you want to save money and buy a good introduction especially about C# or you are an experienced programmer that ventures out to .NET and C# for the first time then it could be a good purchase, otherwise it's better to focus on the topics you are looking for and buy more specialized publications. A professional programmer could find it a little superficial in some parts and due to the usual hurry of Wrox Press to be first on target a little disjointed in others.
said
The writing of this book is too verbose. Some sentences contain more than 5 commas and I thought I was getting lost. It's very difficult to know what the author is trying to explain with those extremly long sentences.
Many examples are not adequate at all. Some of the logics in the examples are so bad, I couldn't see why the author added these to the book. They rather confuse you than helps you understanding the concepts behind C#.
I am sorry but it does look like a rough draft rather than a finished book.
said
The writing of this book is too verbose. Some sentences contain more than 5 commas and I thought I was getting lost. It's very difficult to know what the author is trying to explain with those extremly long sentences.
Many examples are not adequate at all. Some of the logics in the examples are so bad, I couldn't see why the author added these to the book. They rather confuse you than helps you understanding the concepts behind C#.
I am sorry but it does look like a rough draft rather than a finished book.
Comments