Debugging ASP.NET

Rating:
Summary: Awesome
Review: I am a professional web developer and I have spent thousands of dollars on books to stay up to date on my knowledge, and this book is bar far one of the best that I have read yet.

This books goes into detail about the gotchas that most other books fail to mention.

I highly recomend it!

Rating:
Summary: Great Book
Review: I have spent thousands of dollars on books and classroom training to improve my programming skills. It is very rare that any book or any instructor will spend very much time on the debugging process of the language being taught. For me this leaves a lot of the beginning programmers short on their skills, since debugging is 50% of what you do all day. This book gives you a great start on learning the process of debugging an ASP.Net web application and helps you past some of the gotchas that you WILL fall into.

If you are going to develop a ASP.Net web application, I highly endorse this book as required reading!

Rating:
Summary: Great Book
Review: I have spent thousands of dollars on books and classroom training to improve my programming skills. It is very rare that any book or any instructor will spend very much time on the debugging process of the language being taught. For me this leaves a lot of the beginning programmers short on their skills, since debugging is 50% of what you do all day. This book gives you a great start on learning the process of debugging an ASP.Net web application and helps you past some of the gotchas that you WILL fall into.

If you are going to develop a ASP.Net web application, I highly endorse this book as required reading!

Rating:
Summary: Good book to learn about gotcha's in ASP.NET
Review: I have to say that even though the book says that its for intermediate to experienced programmers it really should say that it is for beginners to intermediate programmers.
I say that because a lot of debugging skills suggested in this book come with experience to advanced programmers. However this book does list a whole bunch of gotcha's when using not just ASP.NET, but also some of the advanced features of ASP.NET like User Controls and Caching, Http Handlers, etc. This books also lists some pitfalls to be aware of when using Serviced Components (COM+). These features would be useful for Beginners or Intermediates but the Advanced developers of ASP.NET would already be familiar with some of the techniques listed like Tracing, Conditional Compiling, writing to the event log etc.
I would recommend that if you are new to ASP.NET and have just finished reading a book on ASP.NET, pick this book up next to read about some gotcha's when using ASP.NET

Rating:
Summary: Overall good book
Review: 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.

Rating:
Summary: Do not buy this book
Review: 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.

Rating:
Summary: A must-have for writing good applications
Review: This book is very well-done and thought out. It is more than just a reference on how to debug your application, it is also a book on how to write good code! Truly it is a must have! The first chapters go into detail about how to write good code with structured error handling before it goes into how to debug your ASP.NET pages. Useful suggestions on architecture such as not putting business logic in controls are thoughtfully offered.

Later on, the authors discuss how to incorporate event logging, how to effectively use conditional compiles, tracing, etc. The book goes into how to debug just about every technology that will be used in ASP.NET- web services, caching, XML, user controls, databound controls, inline components, namespaces, SOAP, streams, SQL (data access), and even COM+ interop. It also offers brief samples of how to use each of these technologies (in order to explain how to do the debugging) which is helpful.

Rating:
Summary: A must-have for writing good applications
Review: This book is very well-done and thought out. It is more than just a reference on how to debug your application, it is also a book on how to write good code! Truly it is a must have! The first chapters go into detail about how to write good code with structured error handling before it goes into how to debug your ASP.NET pages. Useful suggestions on architecture such as not putting business logic in controls are thoughtfully offered.

Later on, the authors discuss how to incorporate event logging, how to effectively use conditional compiles, tracing, etc. The book goes into how to debug just about every technology that will be used in ASP.NET- web services, caching, XML, user controls, databound controls, inline components, namespaces, SOAP, streams, SQL (data access), and even COM+ interop. It also offers brief samples of how to use each of these technologies (in order to explain how to do the debugging) which is helpful.

Rating:
Summary: Please do not waste time reading this book.
Review: 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

Rating:
Summary: Decent focused book
Review: 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.