The book itself has many problems, and it's difficult to know where to begin. First there are bundles and bundles of errors, far more than documented by Wrox (as usual). Interestingly many of the errors in this version existed in the previous version, so clearly Wrox quality control (if it exists) failed not once, but twice to identify these errors; that's inexcusable. The errors aren't just in the code, or in the explanations, but they are also in the author's knowledge of .NET. For example, they claim shared members can be accessed from instances of a class as well as the class itself, this isn't the case in C#. You can only access shared members via a class, and not an instance. This error is repeated several times, they even make a special point of it for you to note; very embarrassing. Also, there are times when examples don't work, as important information has been left out (writing to an event log springs to mind). The book is disjointed, you get a code example and then you're told an explanation won't be provided at that point as it is covered later in the book, so you end up jumping back and forth, this occurs far to often for comfort. You're also left hanging time and time again as crucial information is left out.

Although this book does attempt to teach C#, the coverage is a bit limited, and in some areas examples are clearly required but are lacking. As another reviewer suggested, it would be better to know C# before using this book, alternatively you may get by if you have a good C# book to hand to help you through (as I did).

Although there are questions at the end of most chapters, there are only answers to about 5 chapters available from Wrox, the answers to the questions for all the other chapters don't exist.

Another big problem is that examples lead you through a mish-mash of classes with no explanations on what the classes are or what they do; no single class within the entire .NET Framework Class Library is covered properly, many are used but not given any mention. The coverage for the classes, that are mentioned in the explanations, is always grossly incomplete. I found that time and time again I had to go to the .NET documentation to find out what the book was leaving out, I honestly spent far more time in the documentation than using the book, as the book kept raising so many questions. Just remember that for each method or property covered there are 20 times that much not covered for that class.

Chapter 14 on server controls tried to get you to run before you could walk (actually it was more sprint before you could crawl), you'll spend hours in the .NET documentation trying to work out the final two big examples in this chapter, what a mess!!! For me this was the worse chapter in the book. For a beginner you need to show small examples, covering the concepts first, before showing a big example, well this chapter skips smaller examples and just chucks two huge and exceptionally poorly explained ones at you. This is really the most idiotic approach when dealing with a beginner.

None of the form controls were covered properly. For instance they give you a small grossly incomplete list of attributes for the label control and then just say the other controls generally use the same ones. When you go to the .NET documentation you find that each form control has a huge volume of very useful attributes you really should know about, they should have made an effort to cover form controls properly.

The different writing styles of the authors does cause confusion, you also realise that some authors aren't as sure of their coding as others. For instance for a Page_Load event some authors include the object and EventArgs parameters but others don't. As a beginner I was wondering if there was a reason why, and which way was correct, but of course you're not told as it's just the authors own style. Wrox should have picked up on the glaringly obvious like this, but unsurprisingly, failed to do so.

Operator overloads has exceptionally poor coverage, no working examples. I actually got the impression the author didn't really know it that well. Chapter 9, which covers 'shared members and class relationships' is pretty poor as well, this is a very important and powerful area of .NET and the author didn't know how to convey this information at all. The examples are useless, the author even states things like 'this example is way off perfection', and, after giving an example that isn't actually the way you should do something would state, 'what we ought to have done'. It leaves you not knowing when you should apply a particular concept or even if you applied it correctly. I could go on and on about the failings in this book, there really are so many issues to raise, but I won't completely bore you.

So much is left out of this book that was required, and would have taken very little effort to include. Unfortunately being first to press seems to be more important to Wrox Press than quality. In all honestly the whole book feels more like an overview look at ASP.NET rather than a tutorial. Should you get this book you better download the .Net Framework SDK as you're really going to need it.

It amazes me that others have given this book such good reviews. The mind boggles as to how they approached this subject. Did they bother to research each class properly? Did they study this book thoroughly, or did they just read it like a novel? Did they actually try the examples bearing in mind many don't work? I never expected this book to have complete coverage, that would be silly, but I did expect the coverage to be much better than this. Ultimately all this book will succeed in doing is giving you a very basic foundation in ASP.NET, and a shaky one at that. The book should have been bigger and far more thorough. I gave the book two stars as opposed to none as you could argue, from time to time, that it might be the nature of the beast rather than the failure of it's authors. The book does have its good points but sadly they're hard to remember as the bad points stand out more.

Finally, when will Wrox Press wake up and release that 'to many cooks spoil the broth'?