Wanderer said
What ever happened to one of the authors? His website went to pot and so did his blog. Quite sad actually. Then again, it goes to show that he probably doesn't care much for his readers and or people trying to report inaccuracies or criticisms of the book.
My vote? Never buy a book from someone that doesn't support their readers and gives them the proverbial finger when they go to the author's own website looking for a way to contact them.
Anonymous said
This book has a great name but the book does not contain any substantial information related to debugging. Most of the information in the book are not for serious programmers.
My strong suggestion is do not buy this book for ASP.NET debugging or for ASP.NET as some of the reviewers have mentioned.
Anonymous said
Title of the book is great and that's what I expected in the book. Unfortunately the book is below standards and if you are serious ASP.NET programmer this book is not for you. I have done extensive ASP and ASP.NET programming and so I am aware of most of the problems that occur nearly everyday when developing large enterprise level applications and I tried to finding these issues and best ways to detect them in this book , sadly it has no mention of the problems nor best suggestion for debugging ASP.NET. Additionally in order to make it a book they have topics highly irrelevant to the actual title which should have been the first chapters of some beginner books
Anonymous said
There are good chapter about Tracing, code structures, and ADO.net debugging, and lot more. A must have for .Net Web developers. Code examples are in both VB and C#. I wish Author have included more code for COM based debugging.
[email protected] said
To a certain extent, I find this title a bit of a misnomer, as this particular tome contains more than simply debugging. It is well structured to relate these additional topics to debugging, but it is a pleasure to go through a book that both covers its subject and many of the peripheral issues that can help you debug, as well.
While this book is not heavy on OO, which would make a nice additional topic, debugging OO or procedural is largely the same.
There is a good mixture of both C# and VB.NET code, which I applaud. It is important to know that debugging is the same, regardless of language.
I do have a slight beef with the amount of code that resides in the ASPX file. This comes from my belief that the separation of code and UI, via a CodeBehind file, is an important part of .NET. You may disagree with this assessment.
There are some good examples of using tracing in your applications. Tracing is a great tool to find where you are having problems. There is also a nice section on logging your application exceptions.
The material on caching, although not completely related to debugging, is a nice addition.
The book, overall, is aimed for more advanced readers. I think a beginner might be able to tackle some of the material, and probably should, but understand that you might get a bit lost if this is your first ASP.NET book.
Comments