Yuck! Many bad designs

It ain't instant results, buddy. It is quick-and-DIRTY results, as the book presents a lot of bad designs. Where is the multi-tier design? Some chapters in the book show how to put those SQL queries right in aspx pages where only user interface code should be in. Some chapters show how to spit datasets out of business logics. Well it is quick, but should you want to expand or fix things, you would have to redesign and code all over again. Trust me I used to do the quick and dirty works many times and got burnt with broken websites.

Parameterized sql query and stored procedure are so little talked about. These allow you to avoid SQL injection attacks 100% even you don't validate user inputs! (but you should).

Consideration of performance gains and hits of their designs are not discussed at all. The book says you can spawn this and that in matter of minutes, but it doesn't tell you that you'll pay the cost later to support more visitors.

There're inconsistencies between different chapters and authors. This is trivial though, but they should explain why some use auto-generated INTEGER while some use UniqueIdentifier to store ID values. Why char(1) not bit data type? Why ntext and nvarchar(MAX)? Why varchar and nvarchar?

I don't recommend this book to anyone. Go with ASP.NET Problem - Design - Solution by Marco Bellinaso

Other Reviews

• Yuck! Many bad designs
• THIS IS IN VB ONLY, PEOPLE!!
• Title and Description of this book is misleading
• Buyer beware